Skip to main content
Glama

Close a review page

close_review

Stops the local HTTP server for a given reviewId, ending the review session and releasing its port.

Instructions

Stops the local HTTP server for the given reviewId.

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": {
      "reviewId": "<reviewId>"
    },
    "name": "close_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
reviewIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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; it does disclose the concrete side effect (terminating a local HTTP server), which is more than the name alone gives. However, it is silent on whether review state or comments survive the shutdown, whether the call is reversible, what error occurs for an unknown or already-closed reviewId, and whether any cleanup is needed first.

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. Its brevity is efficient, though it borders on under-specification rather than tightness.

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 lifecycle-terminating tool with no annotations, no output schema, and an undocumented parameter, the definition omits the essentials an agent needs: relationship to start_review, post-close state of the review, and failure modes. Only the mechanical action is described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only echoes the parameter name ('the given reviewId') without adding type, format, or origin — e.g., that it must match the identifier returned by start_review. It therefore does not compensate for the undocumented schema.

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 concrete verb and object ('Stops the local HTTP server') scoped to a reviewId, which conveys the effect more precisely than the title's vague 'close a review page'. It implicitly separates itself from lifecycle siblings like start_review, though it never names them.

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 guidance on when to call this versus await_review or resolve_comments, no statement of prerequisites (must a review have been started?), and no indication of whether closing is a required cleanup step. The agent must infer the entire call context.

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