Skip to main content
Glama

get_diff

Read a bounded page of a run’s candidate diff, including new files, to review code changes and inspect results.

Instructions

Read a bounded page of the candidate diff, including new files.

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": {
      "run_id": "<run_id>"
    },
    "name": "get_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
run_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and discloses little. It reveals that output is paginated and includes new files, which is useful, but says nothing about read-only safety, size/truncation limits, required run state, or what the returned text looks like.

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

Conciseness4/5

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

One short sentence, front-loaded with the verb and resource, with no filler. It is under-informative rather than bloated, so brevity here is a strength but not a full score.

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?

No output schema and no annotations, so the description is the only documentation for a tool with three undocumented parameters. It omits the meaning of run_id, how large a 'bounded page' is, and how to detect the end of the diff.

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 all three parameters. The phrase 'bounded page' implicitly maps to limit/offset, but the description never names them, gives no defaults, units, or maximums, and leaves run_id entirely unexplained.

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 ('Read') and resource ('the candidate diff') plus a scope qualifier ('a bounded page'). The parenthetical 'including new files' clarifies ambiguity about new-file content. It does not differentiate from siblings such as get_artifacts or read_events, but the verb+resource pair is concrete enough to select on.

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?

No statement of when to use this versus get_artifacts, get_context, or read_events, and no preconditions (e.g., whether the run must be finished). 'Bounded page' only hints at iteration; there is no explicit guidance to page through with limit/offset.

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