Skip to main content
Glama

Archive a request

archive_request
Destructive

Files one CLOSED request away for the buyer. It takes the id of the request. For a request to several dealerships, it also takes the rowKey of the one dealership. No dealership is told, and nobody is notified. An open request is not archived. It does nothing else to the request. It answers { archived: true }.

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": {
      "id": "<id>"
    },
    "name": "archive_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id of the request.
rowKeyNoFor a request to several dealerships: the key of the one dealership.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true annotation by disclosing the social/operational consequences: no dealership is told and nobody is notified. It also bounds the blast radius with "It does nothing else to the request" and reports the exact response shape. For a destructive mutation this is exactly the extra context an agent needs before calling.

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

Conciseness5/5

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

Six short sentences, each carrying a distinct fact: purpose, precondition, conditional parameter, side effects, non-effects, return value. No filler and the most important constraint (CLOSED only) is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers inputs, preconditions, side effects, and the return value inline despite no output schema, which is strong for a two-parameter mutation. The one ambiguity is what actually happens on an open request — an error or a silent no-op — which matters for an agent's error handling.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds a genuine semantic not in the schema: rowKey is conditionally required only for requests sent to several dealerships, whereas the schema simply lists it as an optional property. The id parameter adds nothing beyond the 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?

States a specific verb and resource plus the precondition that makes it valid: "Files one CLOSED request away for the buyer." An agent immediately knows the object of the operation and its scope. It does not distinguish itself from potentially adjacent siblings such as withdraw or requests_stop_dealership, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear trigger condition (only CLOSED requests) and an explicit exclusion ("An open request is not archived"), plus the conditional multi-dealership case. It does not name an alternative tool for the open-request or cancel scenario, so guidance is clear but not fully routing.

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