Skip to main content
Glama

clawbridge_status

Retrieves a single durable task record by UUID so you can inspect its separate execution, delivery, and review states for accurate task monitoring.

Instructions

Read one durable task record. Execution, delivery, and review states are deliberately separate.

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": {
      "taskId": "<taskId>"
    },
    "name": "clawbridge_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. "Read" implicitly signals a non-mutating lookup and the note that execution, delivery, and review states are deliberately separate is genuinely useful behavioral context that prevents conflating one state with overall success, but nothing is said about error behavior for unknown task IDs, permissions, or what the record contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and followed by the one domain caveat that matters. Every sentence carries weight, though the second sentence could be slightly more explicit about how the separation affects interpretation of the returned record.

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?

The tool is simple (one required param) but has no output schema, no annotations, and no parameter documentation, so the description is the only place an agent could learn what a task record looks like or which of the three states to read. It does not provide that, leaving the caller guessing about the response shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single required taskId parameter has 0% schema description coverage — the schema constrains it as a UUID but never says what it identifies or where to obtain it. The description never mentions taskId, so it does not compensate for that gap in any way.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Read one durable task record" gives a specific verb (read), resource (task record) and scope (one), which distinguishes it from list-style siblings such as clawbridge_tasks. It stops short of naming which sibling to use for related reads (e.g. clawbridge_result, clawbridge_review_context), so sibling differentiation is only implied.

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 explicit when-to-use or when-not-to-use guidance and no alternative named. The second sentence about separate states hints at why one would call it, but an agent must infer the routing decision to this tool versus clawbridge_tasks or clawbridge_result entirely on its own.

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