Skip to main content
Glama

Stop with one dealership

requests_stop_dealership
Destructive

Stops one dealership's part of the buyer's request. The dealership is not told, and it gets no more messages from this request. The other dealerships keep going. If it is the last dealership still going, the request ends. Set confirm to true only after the buyer has said which dealership stops and agreed.

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>",
      "rowKey": "<rowKey>",
      "confirm": "<confirm>"
    },
    "name": "requests_stop_dealership"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
rowKeyYes
confirmYesTrue only after the buyer said which dealership stops and agreed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and openWorldHint=false, yet the description adds consequences the annotations cannot convey: the dealership is not notified, receives no further messages, other dealerships continue, and the request terminates if this was the last one. These downstream effects are exactly what an agent needs before committing a destructive call.

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?

Four short sentences, front-loaded with the core effect and its blast radius before the confirmation rule. The only waste is the final sentence duplicating the confirm property description already present in the schema.

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?

The consequences of the destructive action are fully covered, which is the hardest part for a mutation tool with no output schema. However, with no output schema and two undocumented required identifiers, an agent still cannot confidently map values to id and rowKey from this definition alone.

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 33% — only confirm is documented, and the description merely restates that same wording verbatim. The two identifiers, id and rowKey, are opaque in both the schema and the description, leaving the agent to guess which request and which dealership row are targeted.

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

Purpose5/5

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

"Stops one dealership's part of the buyer's request" names a specific verb and a precisely scoped resource — one dealership, not the whole request. The follow-up sentence contrasting with "the other dealerships keep going" makes the scope unambiguous, so an agent can distinguish this from request-level siblings like withdraw or archive_request.

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?

It gives an explicit precondition for invocation: set confirm to true only after the buyer has named the dealership and agreed. That is real when-to-use guidance rather than an implied cue. It stops short of naming an alternative for the request-wide case, so it 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