Skip to main content
Glama

configure_reviews

Set automatic post-completion review behavior for a project: enable or disable reviews, auto-trigger or manual runs, skip failed features, and choose code or architecture checks.

Instructions

Configure automatic post-completion review settings.

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": "configure_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNoEnable/disable automatic reviews
projectDirYesAbsolute path to the project directory
autoTriggerNoAutomatically start reviews when all features complete (default: true). Set to false to trigger manually via run_review.
skipOnFailureNoSkip reviews if any features failed
codeReviewEnabledNoEnable code quality reviews
architectureReviewEnabledNoEnable architecture reviews

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior1/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, and it discloses nothing. It does not say whether settings are merged or replaced, whether omitted booleans reset to defaults, where configuration is persisted, whether a session must exist, or what the call returns — all critical for a mutation tool.

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?

A single front-loaded sentence with no filler or redundancy; the intent lands immediately. Its terseness is a completeness problem rather than a structure problem, so conciseness itself scores well.

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?

For a six-parameter mutation tool with no annotations and no output schema, one sentence is far too thin. An agent gets no sense of required projectDir scoping, default behavior on omitted flags, or the effect of the write, all of which the description should have carried.

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 every parameter is documented in the schema, which sets the baseline at 3. The description adds no meaning beyond that — no explanation of how the flags interact (e.g. skipOnFailure vs autoTrigger) or what enabling codeReviewEnabled actually changes.

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 ('Configure') and a specific resource ('automatic post-completion review settings'), so an agent knows this writes review configuration rather than reading results like check_reviews or get_review_results. It stops short of naming or contrasting any sibling, though, so sibling differentiation is left to inference from names.

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?

The description gives no when-to-use guidance, no preconditions, and no alternate path. Notably, the 'autoTrigger' schema property references run_review as the manual alternative, but the description itself never routes the agent or explains that trade-off.

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