Skip to main content
Glama

clawbridge_result

Retrieve compact verified delivery facts for a task, confirming delivery only when deliveryState is ready rather than relying on worker prose.

Instructions

Return compact verified delivery facts. A task is delivered only when deliveryState is ready; worker prose is not treated as proof.

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_result"
  }
}

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 burden. It does disclose a meaningful behavioral rule — delivery is only proven when deliveryState is ready, and worker prose is not proof — which is genuinely useful. It does not cover what happens with an unknown taskId, error behavior, or what the returned facts look like, leaving real gaps for an unannotated tool.

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 tight sentences, front-loaded with the returning action, then the verification rule. Nothing is redundant, though the second sentence reads as interpretation guidance rather than call-preparation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should convey the shape of the returned facts; instead it only names one field (deliveryState) and leaves the rest of the payload opaque. The verification semantics partially compensate, but an agent still cannot predict the response.

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

Parameters3/5

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

Schema description coverage is 0%, but the single parameter (taskId, uuid) is largely self-explanatory. The description adds no meaning about the identifier, such as whether it must be a task created by this workspace or how to obtain it.

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

Purpose3/5

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

The description states a verb and resource ("Return compact verified delivery facts"), so the gist is a read of a task's delivery status. But "verified delivery facts" is abstract and not differentiated from the sibling clawbridge_verify_delivery, which an agent could easily confuse it with. It falls between vague purpose and clear purpose.

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 statement of when to call this versus checking status, logs, or verify_delivery, and no prerequisites. The only guidance is interpretive (what deliveryState means), not about when to reach for this tool.

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