Skip to main content
Glama

bridge_claim

Claims a task from the shared agent_bridge task board by task ID, optionally attaching a message body and suppressing wake notifications. Use it to take ownership of queued work before replying or handing it off.

Instructions

Execute bridge claim 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_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
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 provided, so the description carries the full burden, yet it discloses nothing about side effects, whether a claim is exclusive or irreversible, what happens to an existing claim, or what the v2 service returns. For a verb like "Execute" that implies a state-changing operation, 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 single sentence is short and front-loaded, but its brevity comes from under-specification rather than economy; there is no wasted words because there is almost no content.

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?

Given a mutation-flavored tool with three parameters, zero schema descriptions, and no annotations or output schema, the definition omits everything an agent would need to call it correctly.

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% for three parameters (task_id, body, no_wake), and the description explains none of them. In particular the meaning of no_wake and the expected content/format of body are left entirely undocumented.

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 claim through the v2 service" essentially restates the tool name with a verb (Execute) and the resource (bridge claim); the only added information is that a "v2 service" is involved, which does not tell an agent what a claim actually is or what executing one does. It does not distinguish this tool from siblings such as bridge_wake, 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 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 use this tool versus the many bridge_* siblings, no preconditions, and no exclusions. The description gives the agent nothing to route on beyond the name.

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