Skip to main content
Glama

Show change

code_getChange
Read-only

One change: who made it and why, and a unified patch for each text file it touched.

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": {
      "tree": "<tree>",
      "changeId": "<changeId>",
      "org": "<org>"
    },
    "name": "code_getChange"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization whose trees and sites to use. Required on every call, even when only one organization is listed; a path never names it.
treeYesThe tree's name.
changeIdYesThe change's ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds real value by disclosing the return content (author, rationale, per-file unified patches) and the 'text file' qualifier that implies binary files get no patch. It does not address behavior for unknown changeIds, large diffs, or truncation.

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?

A single front-loaded sentence with no filler; the key concept ('One change') leads. The compressed colon construction is slightly fragmentary but still readable and efficient.

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

Completeness3/5

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

With no output schema, the description must carry return-value explanation, and it sketches the record's author, rationale, and patches. It leaves gaps: the full field set is unknown, and it doesn't say how failures or non-text files are reported. Adequate but not complete for a tool with no output schema.

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?

The schema has 100% description coverage, including the org slug's mandatory-every-call note, the tree name pattern, and changeId semantics. The description mentions none of the three parameters, so the baseline 3 applies: the schema does all the work.

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 names a specific verb+resource combination: retrieve one change, including author and rationale, plus a unified patch per affected text file. 'One change' implicitly distinguishes it from the plural listing sibling code_changes, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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?

Usage is only implied: 'One change' suggests this is the single-record fetch versus the list tool, but the description never says when to prefer this over code_changes or code_history, nor does it mention prerequisites such as needing a valid changeId.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources