Skip to main content
Glama

bridge_board

Run the shared local SQLite task board so Claude Code and Codex can exchange tasks, questions, reviews, and replies.

Instructions

Execute bridge board 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_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

D1.5/5.0
Behavior1/5

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

With no annotations provided, the description carries the full behavioral burden, yet it discloses nothing: not whether this mutates state, what permissions or auth are required, whether the operation is reversible, what happens on failure, or what is returned. An agent cannot judge the risk of calling it.

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 single sentence is short but effectively empty; brevity comes from under-specification rather than efficient communication. Nothing is front-loaded because nothing informative is present.

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?

A tool with an undocumented parameter, no annotations, and no output schema needs a description that explains both effect and return; this one supplies neither. It is completely inadequate for correct invocation.

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?

There is one parameter, "project," with 0% schema description coverage, and the description never mentions it. With low coverage the description must compensate, and here it adds no meaning, format, or constraint for the parameter.

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 board through the v2 service" restates the tool name with a verb that carries no defined meaning here; nothing says what a "bridge board" is or what executing it produces. It does not distinguish this tool from the many bridge_* siblings such as bridge_status or bridge_show.

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 offers no when-to-use guidance, no prerequisites, and no indication of when a sibling like bridge_status or bridge_show would be the better choice. The only added phrase, "through the v2 service," is an implementation detail that gives the agent nothing actionable.

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