Skip to main content
Glama

run_agents_parallel

Executes multiple sub-agents in parallel for comparison, task sharing, or mutual review, with concurrency capped by the maxConcurrent policy.

Instructions

複数のサブエージェントを並列実行する(同時実行数はポリシー maxConcurrent で制限)。比較・分担・相互レビューに使う

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": {
      "runs": "<runs>"
    },
    "name": "run_agents_parallel"
  }
}

Input Schema

NameRequiredDescriptionDefault
runsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses one genuinely useful trait — concurrency capped by policy maxConcurrent — but says nothing about whether the call blocks until all runs finish or returns handles, what happens when one run fails, or how results are delivered, despite siblings like wait_agents and get_agent implying an async mode exists.

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

Conciseness5/5

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

Two short sentences with the core action front-loaded and the concurrency constraint attached inline. Nothing is redundant and nothing is buried.

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

Completeness2/5

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

This is a high-complexity tool — batched parallel execution with per-run provider, model, permission, timeout, conversation, and notification options — with no annotations and no output schema. The description covers only the headline action and a policy note, leaving the batch semantics, sync/async behavior, and result shape unexplained.

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

Parameters2/5

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

The single top-level parameter `runs` is an array of up to 10 objects with a required provider/model/task triple, yet the description explains none of this structure, the item cap, or the required fields. Some nested fields do carry schema descriptions, but the key structural parameter is undocumented and the description does not compensate.

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 gives a specific verb and resource in 'run multiple sub-agents in parallel', and the 'multiple/parallel' framing implicitly separates it from the singular run_agent sibling. It is clear what the tool does, though it never names a sibling explicitly to reinforce the distinction.

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 names three concrete usage contexts (comparison, division of labor, mutual review), which is real when-to-use guidance rather than a restatement of the name. It gives no exclusions or explicit alternative (e.g. 'use run_agent for a single task'), so it stops short of the top score.

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