Skip to main content
Glama

revue_log

Lists recent commits on a branch or across all branches, with paging and limits. Use it to review what changed in a repo's history before inspecting diffs or opening changes.

Instructions

Recent commits on a branch (default: the checked-out one), or on all branches.

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

Input Schema

NameRequiredDescriptionDefault
allNoCommits from all branches.
gitNofalse opens the folder as a plain folder (its files only, including .git) even inside a git repo, like revue --no-git. Default true.
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.
skipNoSkip this many first, for paging.
limitNoHow many commits (default 30, which 0 means too).
branchNoBranch or ref to list (default: HEAD).
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

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It mentions branch scope but omits read-only nature, ordering, pagination behavior, and especially the persist/server-lifetime side effect implied by the persist parameter.

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?

A single, front-loaded sentence with no filler. It gives the core scope immediately.

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

Completeness2/5

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

The tool has seven parameters including persist, git, and repo, and no output schema. The one-line description does not explain server-lifetime behavior, plain-folder fallback, or paging, so an agent lacks context for correct invocation beyond schema field docs.

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 the schema already documents all seven parameters. The description adds only branch-scope context (default branch vs all branches), not additional meaning for git, repo, skip, limit, or persist.

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 states the resource (commits) and scope options (a branch, default checked-out branch, or all branches). The verb is implicit in 'log' rather than stated, and it does not distinguish itself from siblings such as revue_changes or revue_diff.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives, and no exclusions. It only describes branch defaults, leaving the agent to infer that this is for commit history rather than working-tree changes or diffs.

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