Skip to main content
Glama

court_replay_gate

Verifies blast-radius boundaries by replaying baseline and candidate paths to confirm changes cause no unintended side effects.

Instructions

Step 3a: Zero-cost replay gate and blast-radius boundary verification.

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": {
      "baseline_path": "<baseline_path>",
      "candidate_path": "<candidate_path>"
    },
    "name": "court_replay_gate"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_pathNo
expectationsNo
baseline_pathYes
changed_filesNo
candidate_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/5.0
Behavior2/5

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

With no annotations supplied, the description bears full responsibility for behavioral disclosure. 'Zero-cost' hints at a non-mutating gate, but it does not explain whether the tool reads files, what permissions are needed, what happens when the gate fails, or what the blast-radius boundary check actually evaluates.

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

Conciseness3/5

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

The single sentence is compact and front-loads the step number, so there is little wasted wording. However, its extreme terseness and unexplained jargon make it structurally unhelpful rather than efficient.

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

Completeness1/5

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

This is a multi-parameter verification tool with no annotations and no output schema, yet the description provides only a cryptic step label. It omits required inputs, expected behavior, failure semantics, and return information, making it inadequate for correct invocation.

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

Parameters1/5

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

The input schema has five parameters with zero percent description coverage, and the description mentions none of them. It provides no meaning for baseline_path, candidate_path, plan_path, expectations, or changed_files, leaving the agent entirely dependent on bare parameter names.

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

Purpose2/5

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

The description identifies a workflow step and uses jargon like 'replay gate' and 'blast-radius boundary verification,' but it never states the concrete operation or resource in plain terms. An agent cannot confidently distinguish this from court_verify_evidence or other verification siblings based on the text alone.

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?

The 'Step 3a' prefix implies an ordered workflow context, but there is no guidance on when this gate should be invoked versus another verification tool, no prerequisites, and no exclusions. Any alternative-routing decision is left entirely to inference.

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