Skip to main content
Glama

compare

Destructive

Runs the same reproducer before and after a code repair and records both exit codes to verify whether the fix resolves the regression.

Instructions

Run the identical reproducer before and after repair; record both exit codes.

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": {
      "session": "<session>",
      "command": "<command>"
    },
    "name": "compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandYes
sessionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already mark this as non-read-only and destructive. Beyond that, the description adds useful behavior: the reproducer is executed twice, before and after repair, and both exit codes are recorded. It still omits side-effect details, failure handling, and authentication requirements.

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?

It is a single compact sentence with the action and outcome front-loaded and no filler. Any remaining ambiguity comes from missing context rather than wordiness.

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 two-required-parameter tool with no output schema, the definition does not explain session semantics, what the 'repair' state means, how the two runs are sequenced, or what is returned beyond exit codes. That is not enough context for reliable invocation.

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 coverage is 0%, so the schema does not explain 'command' or 'session'. The description hints that the command is the reproducer, but it never maps the parameters or clarifies what 'session' represents, leaving invocation under-specified.

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 states a specific action—run the same reproducer before and after repair—and a concrete outcome—record both exit codes. It is clearer than the generic name 'compare', though it does not explicitly distinguish itself from sibling reproducer/check 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 use case is implied: comparing exit codes across before/after repair states. However, it gives no explicit when-not-to-use guidance, prerequisites, or alternatives such as reproducer or check, so overlap with siblings remains ambiguous.

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