Skip to main content
Glama

run_review

Trigger code and architecture reviews for a project directory at any time, such as after finishing features, and optionally re-run completed reviews.

Instructions

Manually trigger code and/or architecture reviews. Can be called at any time, but typically after features complete.

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

Input Schema

NameRequiredDescriptionDefault
forceRerunNoRe-run even if reviews already completed (default: false)
projectDirYesAbsolute path to the project directory
reviewTypesNoTypes of reviews to run (default: both)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it only says the tool can be invoked at any time. It is silent on whether the call is synchronous or long-running, whether it consumes resources or blocks other work, how existing results are treated (only obliquely hinted by the forceRerun parameter), and what happens if reviews are already running.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short, front-loaded sentences with the action stated first and timing second; nothing is padded or redundant. The second sentence is marginally low-value but still earns its place as workflow guidance.

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?

For a trigger tool with fully documented, non-nested parameters and no output schema, the definition covers the essentials. The main gap is that an agent lacks any sense of whether the invocation is blocking or how long it runs, which matters for a review-execution tool without annotations.

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 all three parameters (projectDir, reviewTypes, forceRerun) are already documented in the schema. The description adds no syntax, format, or edge-case detail 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ("Manually trigger") and names the resource scope ("code and/or architecture reviews"), which reads clearly against configure_reviews or get_review_results. It stops short of explicitly differentiating itself from those siblings, so an agent must infer that this one actually executes rather than configures or reads results.

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?

It offers a timing hint — "Can be called at any time, but typically after features complete" — which implies a workflow position. However, it names no alternatives (e.g., versus configure_reviews or check_reviews) and gives no conditions under which the tool should not be used, so guidance remains implied rather than explicit.

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