Skip to main content
Glama

bridge_doctor

Run diagnostics for agent_bridge connectivity, configuration, and shared SQLite task-board health, returning checks that help resolve issues between Claude Code and Codex.

Instructions

Execute bridge doctor 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_doctor"
  }
}

Input Schema

NameRequiredDescriptionDefault
strictNo

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 provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing. It does not say whether the operation is read-only or mutating, whether it touches state, what permissions it needs, or what it returns.

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 with no filler, but the brevity reflects under-specification rather than efficiency. Nothing is front-loaded because there is no substantive information to front-load.

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 tool with an undocumented parameter, no annotations, and no output schema, the description supplies none of the context an agent needs to invoke it correctly. It is effectively a bare name with a service tag.

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?

The single parameter "strict" has 0% schema description coverage, and the description never mentions it or explains what strict mode changes. The agent is left to guess the meaning and default behavior of the only input.

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 doctor through the v2 service" restates the tool name and adds only a service-version reference. It never says what bridge doctor actually does — diagnostics, health check, repair, or otherwise — so an agent cannot distinguish it from siblings like bridge_status or bridge_clean.

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 guidance, no prerequisites, and no mention of any alternative tool or condition that would select this one. The phrase "through the v2 service" conveys no situational context.

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