Skip to main content
Glama

What changed, by meaning, and what it breaks

godot_diff
Read-onlyIdempotent

Compares Godot files by meaning instead of raw text, listing added, removed, moved, or changed nodes, properties, scripts, settings, and shaders while flagging references to removed items.

Instructions

A diff you can read, against git (default: the files on disk against HEAD), offline. A text diff of a .tscn is mostly noise (ids renumbered, sections moved); this compares what the files mean. Scenes and resources: nodes added, removed, moved or renamed, each changed property with resource ids resolved to paths and a changed sub-resource opened up (shape.radius 12 -> 16), groups, children reordered (the 2D draw order), connections, what the file loads; a file whose text changed but not its meaning is one line. Scripts: functions, signals, variables, constants and enums added, removed or changed, and the functions whose code changed. project.godot: settings, input actions and autoloads. Shaders: uniforms and functions. And for everything removed, what still uses it, marked !: a scene connection to a function that is gone (an error at load), an @export value still saved in a scene (dropped silently), a material that still sets a removed uniform, an input action or autoload code still asks for, callers of a function whose argument count changed, files that name a deleted file. Run it after a set of edits and before you call the work done, to check you changed only what you meant to; ref and to compare other commits (a review of a branch), against compares one file with another without git. It is an error when something is marked !. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "godot_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoa second commit: compare two commits instead of a commit with the files on disk
refNothe commit to compare with (default HEAD), e.g. HEAD~1 or main
pathNoproject folder, or a file or folder inside it (relative to the server's folder; default: the current project)
filesNoonly these res:// files or folders (default: everything that changed)
detailNobrief (capped lists) or full (everything); default full
againstNowith exactly one file in files: the earlier version as another file, instead of git

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavior beyond that: it works offline, it flags knock-on breakage with `!` markers (load-time errors, silently dropped exports, dangling uniforms), and it treats `!` findings as errors — context the annotations cannot convey.

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?

Front-loaded with the core claim and the value proposition, and the long middle sentence is a deliberate inventory rather than filler. It is dense and some sentences run long, but no sentence is purely redundant and the usage guidance lands at the end where it belongs.

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

Completeness5/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 carries the burden of describing results, and it does: per-domain breakdowns of what gets reported, the `!` marker convention, and the note that text-changed-but-meaning-same collapses to one line. That is enough for an agent to invoke it and interpret the response correctly.

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 six parameters are already documented in structured form. The description restates the roles of `ref`, `to` and `against` in workflow terms (review a branch, compare one file with another outside git), which is mildly useful but largely overlaps the schema text. `files`, `path` and `detail` are not elaborated at all.

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

Purpose5/5

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

States a specific verb and resource — a semantic diff of Godot project files against git — and explicitly distinguishes itself from a plain text diff ('a text diff of a .tscn is mostly noise'). The enumeration of what it compares (scenes, scripts, project.godot, shaders) makes the scope unambiguous.

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?

Gives concrete when-to-use guidance: run after a set of edits and before declaring work done, to confirm you changed only what you meant; use `ref`/`to` to review a branch; use `against` to compare one file with another without git. It doesn't name any sibling tool as an alternative or set explicit exclusions, which keeps it below a 5.

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