The orchestrator
When a lead agent has reporters, muxAI automatically injects two MCP tools and a team roster into the lead’s system prompt. The lead doesn’t need to know internal tool names. It just sees instructions like:You have direct reports. Use the orchestrator tools to coordinate them.
Tools
run_team
Invokes all reporters in parallel. Each reporter runs their own configured default prompt. Returns every reporter’s name, role, status, and full output. Use this to gather initial findings from the whole team.
ask_reporter
Invokes one reporter by name. Optionally pass a
task to override their default prompt. Use this for targeted follow-ups, re-runs, or when you need to provide specific context (e.g. a chart URL or asset pair).When to use which
| Scenario | Tool | Why |
|---|---|---|
| Initial data gathering | run_team | Fires all reporters in parallel, one turn |
| Follow-up question to one analyst | ask_reporter | Targeted, with optional task override |
| Lead provides per-reporter context | ask_reporter | Each reporter gets tailored input (asset, chart, timeframe) |
| Resolve conflicting findings | ask_reporter | Re-run the analyst whose data you want to verify |
Name matching
ask_reporter requires the exact agent name (not the role). If the lead gets the name wrong, the orchestrator returns an error listing available reporter names. The lead self-corrects on the next turn.
Turn cost
Each tool call and response consumes one turn. Understanding turn cost helps you set appropriatemaxTurnsPerRun values:
| Action | Turns used |
|---|---|
run_team (success) | 1 |
ask_reporter x3 (all succeed) | 3 |
ask_reporter with wrong name + retry | 2 |
| Wrong names for 3 reporters + retry all | 4-6 |

