Skip to main content
Glama

revue_stop

Stop the Revue server for a repository only if an MCP server started it, leaving manually started servers untouched.

Instructions

Stop the revue server for a repo, if this MCP server or an earlier one started it. Servers the user started by hand are left alone.

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

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.7/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load; it does disclose the key trait that the call is conditionally a no-op when the server was started manually. It omits what happens if no server is running, whether in-flight work is interrupted, and what the call returns.

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?

Two short sentences with zero waste, and the conditional ownership rule is front-loaded in the first sentence where it matters most.

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

Completeness3/5

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

A two-parameter, no-output-schema, no-annotation tool where the description covers the main ownership condition but leaves out result/return behavior and the no-server-running case. Adequate but with visible gaps for a lifecycle tool.

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 explains 'repo' and 'git' in detail. The description adds no parameter-level meaning, not even noting that an omitted repo defaults to the current directory. Baseline 3 applies.

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 ('Stop the revue server for a repo') and pairs it with the scope condition. The 'stop' framing implicitly complements siblings like revue_open, though no sibling is named explicitly.

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 a clear condition for when the tool acts ('if this MCP server or an earlier one started it') and an explicit exclusion ('Servers the user started by hand are left alone'). No alternative tool is named, so it stops short of full routing guidance.

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