Skip to main content
Glama

revue_status

List running Revue servers for all repositories or a single repo, showing each server's port, lifetime, note storage and open tabs so you can find and connect to the right browser session.

Instructions

List running revue servers (all repos, or one), with their port, lifetime, note storage and open tabs.

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

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.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'List' implies a safe read, and the return fields (port, lifetime, note storage, open tabs) are disclosed, but nothing is said about behavior when no servers are running, permissions, or cost.

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 the verb and scope up front and the returned fields compactly parenthesized. No filler or redundancy.

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?

With two optional parameters fully covered by the schema and no output schema, the description does enough by enumerating the per-server fields an agent will receive. Only minor gaps remain around empty-state behavior.

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 both the 'git' and 'repo' parameters are already fully documented in the schema. The description's '(all repos, or one)' loosely maps to 'repo' but adds no syntax or semantics beyond the schema, so the baseline 3 applies.

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 — 'List running revue servers' — and scopes it ('all repos, or one'), while enumerating what each entry contains (port, lifetime, note storage, open tabs). This clearly separates it from mutation siblings like revue_open and revue_stop.

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?

The parenthetical 'all repos, or one' implies you can narrow scope to a single repo, which hints at usage. However, there is no explicit statement of when to call this versus alternatives such as revue_show or revue_annotations, and no exclusions or prerequisites.

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