Skip to main content
Glama

bridge_done

Marks a bridged task as completed by task ID, optionally attaching result details or files and controlling wake notification.

Instructions

Execute bridge done 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_done"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesNo
resultNo
no_wakeNo
task_idYes

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 burden and discloses nothing: not whether this mutates state, whether it is idempotent, whether it requires ownership of the task, or what happens to files/result payloads. Given the name implies a state transition on a task, this is a serious gap.

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 sentence is short, but its brevity is under-specification rather than concision — it spends its only clause on restating the name. There is no front-loaded statement of effect or scope.

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 four undocumented parameters, no annotations, and no output schema, the description would need to explain the completion workflow and parameter effects; it explains none of it. An agent could only guess at 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?

Schema description coverage is 0% across four parameters, and the description does not mention task_id, files, result, or no_wake at all. The most consequential parameter (no_wake, which presumably suppresses a wake notification) is completely unexplained anywhere.

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 done through the v2 service" only restates the tool name in slightly different words; it never says what "done" means (completing a task? marking it finished?) or what resource is affected. An agent cannot distinguish this from siblings like bridge_claim or bridge_clean based on this text.

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 guidance on when to call this, what preconditions exist (e.g., that the task must be claimed first), or which sibling to use instead. The single sentence offers nothing an agent could act on for routing decisions.

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