Skip to main content
Glama

clawbridge_record_review

Records a human or Codex review conclusion for the exact verified task SHA, capturing review notes without merging a PR or replacing GitHub approval.

Instructions

Record a human/Codex review conclusion for the exact verified task SHA. It never merges a PR or substitutes for a GitHub approval.

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>",
      "outcome": "<outcome>",
      "note": "<note>"
    },
    "name": "clawbridge_record_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYes
taskIdYes
outcomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the tool records a review conclusion, relies on an exact verified task SHA, and never merges a PR or substitutes for GitHub approval, but it does not cover permissions, permanence, idempotency, or the effect of each outcome.

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?

The description is two front-loaded sentences with no wasted wording. The purpose is stated first followed by a critical boundary condition.

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 mutation-style tool with no annotations, no output schema, and three required parameters at 0% schema coverage, the description is too thin. It provides the high-level boundary but omits parameter meaning, expected effects, and operational details an agent would need to invoke it 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 three required parameters. The description mentions a 'verified task SHA' but does not explain how that maps to taskId (a UUID), what reviewed versus changes_requested mean behaviorally, or what should be included in note.

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 uses a specific verb and resource: recording a human/Codex review conclusion for the exact verified task SHA. It also distinguishes the operation from merging a PR or acting as a GitHub approval, though it does not explicitly distinguish itself from siblings such as clawbridge_check_review_head or clawbridge_review_context.

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 description implies the tool should be used to record a review conclusion and not to perform a merge or GitHub approval. However, it does not state when to use this tool versus nearby review-related siblings, nor does it describe prerequisites beyond the 'verified task SHA' phrase.

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