Skip to main content
Glama

clawbridge_check_review_head

Verify that a reviewed task worktree still points at the reviewed SHA; if HEAD changed, invalidate the recorded review and return the task to pending.

Instructions

Check whether the reviewed task worktree still points at the reviewed SHA. A changed HEAD invalidates the recorded review and returns it to pending.

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

Input Schema

NameRequiredDescriptionDefault
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description importantly discloses that this check can mutate state: a changed HEAD invalidates the recorded review and returns it to pending. It does not explain the unchanged-HEAD outcome, idempotency, or possible result and error behavior.

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 compact sentences front-load the check and immediately state its critical side effect. There is no redundant or distracting wording.

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

Completeness4/5

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

For a one-parameter tool, the description covers the target, comparison, and non-obvious review-state transition needed to invoke it correctly. Response shape, unchanged-HEAD behavior, and more explicit workflow timing remain undocumented.

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?

The sole taskId parameter has no schema description beyond its UUID constraints, and the description only indirectly explains it through the phrase 'reviewed task worktree.' That makes the target inferable, but it does not explicitly map taskId to the reviewed task or indicate where to obtain the identifier.

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?

The description precisely identifies the operation and resource: checking whether a reviewed task worktree still matches its reviewed SHA. The invalidation consequence further narrows its role, although it does not explicitly differentiate the tool from sibling review or status tools.

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?

The wording implies use when revalidating an existing recorded review after the worktree may have moved. It does not state where this check belongs in the workflow, when it is unnecessary, or which alternative to use for other review or status needs.

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