Coordinator
In one line: It orchestrates other agents or tools over MCP and makes a go/no-go call with a human.
What it is
A Coordinator does not do the work itself. It talks to other agents and tools, usually over MCP, gathers what each one says, puts the answers together and proposes a decision such as go or no-go. A person confirms.
How one run goes
- Get a question that spans systems, such as “are we ready to launch?”.
- Ask each specialist agent or tool for its status.
- Collect the answers; spot conflicts and missing replies.
- Summarise them as one view with a recommendation.
- A person gives the go or no-go; the Coordinator records it and follows up.
An example
Before a campaign launches, the Coordinator asks the content, search and performance tools how they are doing. One has not answered, so it proposes “hold” and says why.
Where the human comes in
A human gives the go/no-go; the agent only gathers status and proposes.
Use it when
Several systems or teams each hold part of the answer. It is not the right shape when one data source has all of it.
Watch out for
Every tool it can reach widens what it can do, so give it only what the job needs, and never let it decide alone.
Back to all patterns or the Idea Gallery. A pattern is a shape to borrow when it fits, not a category: the gallery cards do not carry one.