Skip to main content
Glama

bridge_review

Submit a bridge review verdict (approve or changes) for a task through the v2 service, optionally including a body.

Instructions

Execute bridge review through the v2 service.

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": {
      "task_id": "<task_id>"
    },
    "name": "bridge_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
no_wakeNo
task_idYes
verdictNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

D1.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses almost nothing. "Execute" weakly suggests an action, but there is no mention of whether this is a write/side-effecting call, what verdict does, what no_wake suppresses, permission requirements, or what happens on success — none of which the annotations cover.

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 a single short sentence, but its brevity comes from under-specification rather than economy — no sentence earns informational value here. There is no structure or front-loading of scope because there is no scope stated.

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?

For a 4-parameter tool with an enum, a required task_id, no annotations, and no output schema, the description omits everything an agent needs to call it correctly. Neither inputs, effects, nor return behavior are addressed.

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% across 4 parameters, and the description explains none of them. task_id, body, verdict, and no_wake are all left without semantics; in particular no_wake and the approve/changes enum's effect are completely unexplained anywhere in the definition.

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?

"Execute bridge review through the v2 service" essentially restates the tool name (bridge_review) and adds only a service version. It never says what a "review" is here, despite the schema implying the agent submits a verdict (approve/changes) with a body, which would let an agent distinguish this from siblings like bridge_answer or bridge_done.

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?

No when-to-use guidance, no prerequisites, no mention of any alternative. "Through the v2 service" is not a usage condition; an agent would have to guess whether this is the correct tool versus bridge_answer, bridge_done, or bridge_log.

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