Skip to main content
Glama

clawbridge_verify_delivery

Validates a completed task's remote Git worktree before delivery by checking it is under the registered worker allowlist and on a non-default branch.

Instructions

Verify a completed task's remote Git worktree before delivery. The worktree must be under the registered worker allowlist and on a non-default branch.

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>",
      "worktreePath": "<worktreePath>"
    },
    "name": "clawbridge_verify_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes
worktreePathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the two validation rules (worker allowlist, non-default branch), which is genuinely useful, but says nothing about whether the call is read-only or mutating, what happens when the worktree is outside the allowlist, whether it fails fast or returns diagnostics, or whether it has side effects on the worktree.

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

Conciseness5/5

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

Two tight sentences, front-loaded with the core action and followed by the gating constraints. No filler, no restatement of the tool name.

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?

For a validation/gate tool with no output schema, no annotations, and 0% parameter documentation, the description leaves too much open: it does not say what a successful or failed verification looks like, whether it blocks delivery or merely reports, or how the path argument is interpreted. An agent could invoke it but could not interpret or act on the result confidently.

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?

Schema description coverage is 0% for both required parameters. The description never clarifies what worktreePath means in practice — absolute vs. relative, local vs. remote path, and whether it must align with the registered worker's allowlist root — nor how taskId relates to the worktree. With a low-coverage schema, the description needed to compensate and does not.

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?

Specific verb + resource: 'Verify a completed task's remote Git worktree before delivery' tells the agent exactly what operation runs and on what artifact. It is distinguishable from siblings like clawbridge_check_review_head or clawbridge_preflight by naming the worktree/allowlist concern, though it does not explicitly name an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Before delivery' implies the timing and context of use, and 'completed task' implies a precondition. However, there is no explicit statement of when not to use it, what to do if verification fails, or which sibling to reach for instead (e.g. preflight vs. check_review_head).

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