Skip to main content
Glama

What changed since a version

what_changed
Read-onlyIdempotent

What changed in a file between the version you have and the newest one (or any two saved versions): how many versions sit between them, the grade before and after, lines added and removed, and the changed lines themselves. Pass since as a sha256 (or its first 7+ characters, the form mdr.lock records) or a version label. Use it before you update a pinned skill, so the change is read before your agent runs it.

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": {
      "ref": "<ref>",
      "since": "<since>"
    },
    "name": "what_changed"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOptional: compare to this version instead of the newest.
refYesowner/repo/name for a skill (anthropics/skills/pdf), owner/repo/path for any other file (vercel/next.js/AGENTS.md), or an art_ id from find_files.
sinceYesThe version you have: sha256, a sha256 prefix of 7+ characters, or a label like git:20260913.ab12cd3.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real substance beyond that by disclosing the return payload and the accepted identifier forms, including the mdr.lock convention. It says nothing about large-diff truncation or behavior when the reference or version resolves to nothing, which keeps it from a higher score.

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?

The payload is front-loaded in the first sentence and the identifier rules and usage motive follow in logical order. Sentences are dense but each carries distinct information. The trailing rationale about reading the change before the agent runs is slightly padding but supports the usage rule.

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

Completeness4/5

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

With only three parameters, no output schema, and no nesting, the description is sufficient: an agent knows the inputs accepted, the fields returned, and the situation that warrants a call. Remaining gaps are about edge cases such as unresolved references or oversized diffs, not about whether or how to call it.

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?

Schema coverage is 100%, so all three parameters are already documented, which sets the baseline at 3. The description does add meaning: since can be a full sha256, a 7+ character prefix, or a label, and it notes the prefix form mirrors what mdr.lock records. It never mentions the optional to parameter, leaving that entirely to the schema.

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 opens with a specific verb+resource and scope: what changed in a file between two saved versions. It also enumerates exactly what comes back (version gap, grade before/after, lines added/removed, changed lines), which lets an agent distinguish it from a plain version-listing tool. It does not name a sibling like file_history or get_file as the alternative, so differentiation is inferred rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete triggering situation: call this before updating a pinned skill so the change is read before the agent runs it. That is actionable context rather than vague guidance. It stops short of stating when not to use it or which sibling covers adjacent needs.

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