Skip to main content
Glama

Close a request

closeRequest
Destructive

Stop accepting answers. Pending links show a closed page.

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": {
      "requestId": "<requestId>"
    },
    "name": "closeRequest"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful context — that pending links render a closed page — but omits whether the close is reversible, whether answers already collected are retained, and what a caller sees on success.

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 sentences with the primary effect front-loaded and the recipient-visible consequence second. No filler, though the second sentence is terse enough to border on ambiguous ('closed page' is not defined).

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?

This is a destructive, non-read-only mutation with no output schema and no annotation-level detail beyond the hint flags. For that profile the description should say whether the action can be undone and what happens to already-submitted answers; it says neither.

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% for the single required parameter requestId, and the description never mentions it or its expected format (ID vs. slug vs. URL token). The name is self-explanatory, but the description does nothing to compensate for the documentation gap as required when coverage is low.

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 states a specific state change — stopping acceptance of answers — and its visible consequence (pending links show a closed page). It is unambiguous about what the tool does, but it never names itself as closing a request relative to siblings like updateRequest or previewRequest, so an agent must lean on the title for differentiation.

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 close versus using updateRequest, no mention of prerequisites (e.g., ownership or admin rights), and no stated conditions under which closing is inappropriate. The agent must infer usage entirely from the name and title.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources