Skip to main content
Glama

bridge_who_coordinates

Queries the v2 bridge service to determine which agent coordinates the shared task board, helping Claude Code and Codex route tasks to the correct owner.

Instructions

Execute bridge who-coordinates through the v2 service.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bridge_who_coordinates"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about read vs. write semantics, permissions, side effects, or return shape. Calling something 'who-coordinates' suggests identity/ownership data, but that is inference, not stated behavior.

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

Conciseness2/5

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

It is short, but brevity here comes from under-specification rather than efficiency; 'through the v2 service' is filler that adds no meaning for an agent. There is no front-loaded statement of what the tool actually does.

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

Completeness1/5

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

With zero annotations, no output schema, and an undocumented optional parameter, the description needed to explain purpose, scope, and result format. It does none of these, leaving the definition effectively unusable without outside knowledge.

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

Parameters1/5

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

Schema description coverage is 0% and the sole parameter 'project' is undocumented in both schema and description. The description does not explain whether 'project' scopes results, is optional (it is not required), or what happens when omitted.

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

Purpose2/5

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

The description restates the tool name ('bridge who-coordinates') with the generic verb 'Execute' and adds only 'through the v2 service', which conveys no resource meaning. An agent still cannot tell what 'who-coordinates' returns or how it differs from siblings such as bridge_whoami or bridge_agents.

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

Usage Guidelines1/5

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

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no mention of any alternative among the many bridge_* siblings. The single sentence offers nothing to route a caller between this and bridge_whoami/bridge_agents/bridge_status.

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