Skip to main content
Glama

agy_council_round

Calls up to two selected remote participants via stored channels to collect bounded council replies for a discussion round, using original material and a current plan snapshot.

Instructions

Explicitly call up to two selected remote participants via their stored channels (default first two task remotes). No call is made for client gpt. Codex CLI may be selected independently. Separate attempt budgets; no retries/loop. Collect uses only original material, disallows leading focus, and keeps replies sealed. Later batch shares a pre-call snapshot with full current plan, current task memory and each participant's own last successful contribution. Recent history/questions remain bounded; consult context manifests. May incur cost; CLI tools are not forcibly disabled.

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": {
      "discussion_id": "<discussion_id>"
    },
    "name": "agy_council_round"
  }
}

Input Schema

NameRequiredDescriptionDefault
focusNo
reply_toNo
participantsNo
discussion_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.2

TDQS

B3/5.0
Behavior4/5

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

Annotations declare openWorldHint=true and readOnlyHint=false, but the description adds genuinely non-obvious traits: cost may be incurred, separate attempt budgets with no retries, collection uses only original material, replies are sealed, and CLI tools are not forcibly disabled. These go well beyond the annotations and do not contradict them.

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 core action is front-loaded in the first sentence, which is good, but the remainder is a dense semicolon-separated run of clauses mixing cost, snapshot composition, history bounds, and collection rules. It is short but hard to parse and not organized by concern.

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?

For a complex, open-world orchestration tool with 0% schema coverage and no output schema, the description should explain the parameters and what the agent gets back (messages? statuses?). It covers behavioral rules richly but leaves parameter formats and return shape entirely unspecified.

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?

Schema description coverage is 0% and there are four parameters, so the description must compensate. It only hints that 'participants' takes up to two remote channel names and gestures at 'focus' via 'disallows leading focus' (an ambiguous constraint), while 'reply_to' and 'discussion_id' receive no explanation at all.

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 first sentence states a concrete action (calling up to two selected remote participants through their stored channels) and the tool could be distinguished from generic reads. However, it never explicitly contrasts itself with close siblings like agy_discussion_turn or agy_council_reveal, and the jargon ('collect', 'batch', 'remotes') obscures the core purpose somewhat.

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

Usage Guidelines2/5

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

The description gives operational constraints ('default first two task remotes', 'no call for client gpt', 'no retries/loop') but never states when to use this tool versus alternatives such as agy_discussion_turn, agy_council_assign_roles, or agy_council_reveal. The agent is left to infer the selection condition.

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