Skip to main content
Glama

Multi-agent orchestration plan

submit_multi_agent_orchestration_plan
Idempotent

Split a workflow description into typed steps and produce an orchestration plan and a Mermaid diagram. At design time, to turn a described workflow into steps and a diagram. Do not choose this when you need the workflow executed, which needs the agents. Example requests: Plan the orchestration for this agent workflow. | Turn this workflow into agent steps and a diagram. | Design the multi-agent flow for this process.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_multi_agent_orchestration_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
quote_idNoThe quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
authorized_byYesIdentifier of the human or agent authorizing this job.
accepted_priceNoThe amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

NameRequiredDescriptionDefault
quoteNo
stateYes
job_idYes
artifactsNo
access_tokenNoPer-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
verificationNoIndependent verification. verification.ok = false means the job failed, not a partial success.
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description usefully discloses the key behavioral boundary that this is design-time only and performs no execution, which complements the idempotentHint=true and destructiveHint=false annotations. However, it omits that invocation is a priced, quote-authorized job (quote_id/accepted_price) and says nothing about the asynchronous job/response lifecycle, so an agent could call it without understanding the authorization flow.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is well front-loaded, but the second fragment ('At design time, to turn a described workflow into steps and a diagram') largely restates it, and three example requests add bulk with moderate routing value. The sentence structure is choppy ('which needs the agents'), so trimming would improve clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the design-time versus execution distinction is covered. Still, for a tool whose invocation requires a quote and an authorizing identity, omitting that a quote must be obtained first leaves a material gap between 'this is the right tool' and 'this call will succeed'.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 75% and the nested workflow object is well documented in the schema, so the schema carries most of the burden. The description adds no meaning about any parameter — not the workflow text, not quote_id, not authorized_by — so it does not compensate for the remaining 25% gap or clarify how the workflow string should be phrased beyond the examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and artifact: it splits a workflow description into typed steps and produces both an orchestration plan and a Mermaid diagram. It also draws a boundary against execution ('needs the agents'), which distinguishes it from the submit_job family, though it never names the actual sibling tool that performs execution.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit when ('At design time, to turn a described workflow into steps and a diagram') and an explicit when-not ('Do not choose this when you need the workflow executed'). The alternative is described generically as 'the agents' rather than by tool name, so the routing signal is clear but not directly actionable within the sibling list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources