Skip to main content
Glama

clawbridge_review_context

Builds bounded review context for a delivered task: fixed commit SHA, pull request URL, merge base, diff stats, and changed paths. It gathers review evidence only and never marks the task approved.

Instructions

Build bounded review context for an already delivered task: fixed SHA, PR URL, merge base, diff stat, and changed paths. It never marks the task approved.

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

Input Schema

NameRequiredDescriptionDefault
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 usefully discloses that the tool is non-approving and that the context is 'bounded', but leaves out error behavior for non-delivered or missing tasks, whether the snapshot is cached or re-derived, and any size limits implied by 'bounded'.

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 sentences, front-loaded with the verb and the payload list, with no filler. The clarifying negation about approval is placed where it matters most.

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?

With no output schema and no annotations, the enumeration of returned artifacts does much of the work an output schema would. The remaining gap is failure modes and precise bounds for a read-context tool with one required parameter.

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 coverage is 0% for the single taskId parameter, so the description would need to compensate and does not name it explicitly. 'For an already delivered task' does implicitly tie taskId to a delivered task, which adds a little meaning, but format, source of the ID, and validation behavior come only from the schema.

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?

States a specific verb ('Build bounded review context') plus the resource (a delivered task) and enumerates exactly what the context contains: fixed SHA, PR URL, merge base, diff stat, changed paths. That is concrete enough to distinguish it from the mutating siblings such as clawbridge_record_review, though it never names an alternative directly.

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?

'For an already delivered task' supplies a real precondition, and 'It never marks the task approved' implies that recording approval is a separate step. However, it does not say when to prefer this over clawbridge_check_review_head or clawbridge_verify_delivery, nor what to do if the task is not yet delivered.

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