Skip to main content
Glama

revue_definitions

Find where a function, class, type, or variable is defined at the revision a view shows, with the closest match ranked first.

Instructions

Find where an identifier (function, class, type, variable...) is defined, at the revision a view shows (in a plain folder, in its files). A fast git-grep heuristic, not a compiler: JS/TS, Python, Go, Rust, C-family and shell, with a loose fallback for other languages. The best match comes first, marked with * when it is a clear winner.

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": {
      "name": "<name>"
    },
    "name": "revue_definitions"
  }
}

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.
nameYesThe identifier.
pathNoFile the identifier was seen in; ranks nearby definitions first.
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.
sideNoSearch the new (default) or old side of the view.
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 well: it discloses the heuristic nature ('not a compiler'), the supported language set with a loose fallback, and the result ordering including the '*' winner marker. It stops short of stating permissions, whether it is strictly read-only, or what happens when a server must be started (only the persist param hints at that).

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 tight sentences, front-loaded with the core action, then the accuracy caveat, then the result-ordering contract. No filler and nothing redundant with the schema.

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 10-parameter tool with no annotations and no output schema, the definition covers what matters: what it searches, how reliable it is, and how results are ordered. Remaining gaps — no explicit read-only statement and no mention of the server lifecycle implied by persist — are minor given the fully documented 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?

Schema description coverage is 100%, so the schema already explains git, ref, base, head, mode, side and persist in detail. The description adds only a loose framing that results reflect 'the revision a view shows', without elaborating on how mode/side/path interact. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Find where an identifier ... is defined') and scopes it to 'the revision a view shows', including the plain-folder case. An agent can immediately tell this apart from siblings like revue_diff, revue_log or revue_annotations.

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 implied by the purpose ('find where an identifier is defined'), and the heuristic framing signals when it is appropriate versus a real compiler search. However, it never names an alternative tool or states when NOT to use this, leaving the agent to infer routing from sibling names.

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