Skip to main content
Glama

revue_diff

Generates a unified diff for one changed file or every changed file in a repository view, including untracked working-tree files, so you can inspect changes.

Instructions

Unified diff of one changed file, or of every changed file, in a view of the repo. Includes untracked files in the working tree view. Returns text to you; to show changes to the user, use revue_open or revue_show.

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": "revue_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
gitNofalse opens the folder as a plain folder (its files only, including .git) even inside a git repo, like revue --no-git. Default true.
refNoCommit to show in commit mode (default HEAD).
baseNoBase branch in branch mode (default: main, master, origin/main, origin/master or develop, whichever exists).
headNoBranch to view in commit/branch mode without checking it out (default: the checked-out branch).
modeNoworking = uncommitted changes vs HEAD (default); commit = one commit vs its parent; branch = head vs its merge-base with base, like a PR.
pathNoFile path relative to the repo root. Omit for all changed files.
repoNoAny folder inside the git repo. Defaults to the current working directory. A folder outside any repo opens as a plain folder: its files only, with no changes, history or modes.
contextNoLines of context around changes: a number such as 10 (default 3), or "all" for the whole file.
persistNoIf a server has to be started: true keeps it running after this agent session ends, false stops it with the session. Defaults to the --lifetime setting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does disclose non-obvious behavior: untracked files appear in the working-tree view, output is plain text rather than a UI, and persist controls server lifetime. It omits any warning about very large diffs (e.g. omitting path for all files) or truncation behavior.

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?

Three short sentences, front-loaded with what is returned and followed by the cross-tool routing rule. No filler or restatement of the name.

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?

For a nine-parameter, all-optional read tool with full schema coverage and no output schema, the description adequately explains the return type and display routing. The remaining gap is practical guidance on output size and truncation when diffing every changed file.

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 description coverage is 100%, so every parameter including the mode enum, context, and persist is already documented in the schema. The description adds only the untracked-files nuance, which is marginal beyond the schema baseline.

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 and resource: a unified diff of one file or all changed files within a repo view, with untracked-file inclusion noted. It is distinguishable from the rendering siblings it names, though it does not contrast itself with revue_changes, which an agent might also consider for inspecting modifications.

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?

Explicitly routes the agent: this tool returns text to the agent, while revue_open or revue_show should be used when the user needs to see changes. The mode/git parameters also imply the working vs commit vs branch contexts, but no exclusion against revue_changes is given.

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