Skip to main content
Glama

Close a Request

close_request
DestructiveIdempotent

Close a Request. Popular Demand emails the person a link to reopen it within 7 days.

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": {
      "request_id": "<request_id>",
      "reason": "<reason>"
    },
    "name": "close_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhy the person wants it closed.
request_idYesThe Request’s id from list_requests.
request_keyNoOptional. The same key repeats a change safely; one is derived when left out.
expected_versionNoOptional. The Request version you last read.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior4/5

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

The annotations already declare destructive=true, idempotent=true, and readOnlyHint=false, so the description is not required to establish that this mutates state. It still adds valuable undisclosed behavior: the requester is emailed a reopen link valid for 7 days, which tells the agent the action is externally visible to a person and reversible within a bounded window. It does not say what happens after 7 days or how the required reason code affects downstream handling.

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 no filler, and the most consequential fact (the 7-day reopen link) is stated up front after the action. The opening sentence is a redundant restatement of the title rather than an efficient lead.

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?

An output schema exists, so return values need not be explained, and the description covers the key user-facing side effect. It is still thin for a destructive, notification-triggering mutation: no guidance on when to prefer it over update_request, and no note on what the reason enum drives.

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%, including enum values for reason and notes on request_key idempotency and expected_version, so the schema does the semantic work. The description adds nothing about parameters, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

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

The verb+resource is legible (close a Request), but the first sentence is essentially the title restated and carries almost no information beyond the tool name. It never distinguishes closing from status changes available via update_request or save_request, so an agent gets the action but not its boundaries.

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 statement of when to close versus when to update or save a request, and no prerequisites (e.g., must the request be open, must reason be supplied). With siblings like update_request and save_request present, the absence of any routing guidance is a real gap.

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