Skip to main content
Glama

bridge_status

Check the agent_bridge service status to confirm task exchange availability and diagnose local SQLite task board connectivity.

Instructions

Execute bridge status 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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
onelinerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

D1.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about read-only vs mutating behavior, permissions, side effects, or output shape. The only hint is that work happens "through the v2 service," which does not help an agent predict what happens on invocation.

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?

The one-sentence form is compact, but the brevity here is under-specification rather than efficiency: nothing is front-loaded because nothing informative is said. There is no wasted wording, but there is also no substance to structure.

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?

With no annotations, no output schema, and an undocumented parameter, the definition should explain return content and the oneliner flag. Neither is addressed, leaving the agent guessing about both the call's effect and its result.

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 single optional parameter "oneliner" (boolean) is never mentioned or explained. The description leaves the agent unable to know what setting oneliner changes in the response, so it fails to compensate for the schema gap.

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 status" essentially restates the tool name (bridge_status); the verb "Execute" adds no information about what operation actually occurs. "Through the v2 service" identifies a backend but not the resource's scope or how this differs from siblings like bridge_activity, bridge_show, or bridge_doctor.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. An agent cannot tell from this text whether to call bridge_status or bridge_activity/bridge_show when it wants state information.

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