Skip to main content
Glama

revue_open

Open a browser-based git change viewer on the overview of all changed files. Use it to review code changes for a repo, commit, or branch instead of printing a diff.

Instructions

Open revue, the browser-based git change viewer, on the overview of all changed files. Use this when the user asks to see or review code changes, rather than printing a diff. Starts a revue server for the repo if needed and reuses an open revue tab when there is one.

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_open"
  }
}

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.
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.
newTabNoOpen a new browser tab even if a revue tab is already open.
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.2/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 burden and does disclose a real side effect: it "starts a revue server for the repo if needed" and "reuses an open revue tab." Server lifecycle consequences and any port/auth or blocking behavior are left unstated, which keeps it out of the top band.

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 sentences, each doing distinct work: what it is, when to reach for it, and what it does underneath. The usage guidance is front-loaded ahead of the mechanics with no filler.

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?

Complete on purpose, triggers, and side effects for an 8-optional-parameter tool with no annotations. The remaining gap is that with no output schema the description never tells the agent what comes back (a URL, a tab handle, or nothing), which matters for confirming success.

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% and every parameter already has a detailed description, including the mode enum semantics and the git/ref/base/head interactions. The tab-reuse sentence lightly reinforces newTab's default, but that default is already implied by the schema, so it adds little beyond it.

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?

Names a specific verb and resource ("Open revue, the browser-based git change viewer") and pins the scope to "the overview of all changed files," so the agent knows exactly what surface gets opened. It also implicitly separates the tool from a text-diff sibling with "rather than printing a diff."

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 an explicit trigger ("when the user asks to see or review code changes") plus the alternative it is not meant to replace ("rather than printing a diff"). It stops short of naming which sibling to use for headless diffing, so the routing is clear but not fully closed.

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