Skip to main content
Glama

Sirfus CAR

Cancel a request

car_cancel_request
DestructiveIdempotent

Cancels a request before it goes to a business (while it waits for the text code). After it has gone to a business it cannot be canceled here.

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": "car_cancel_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestIdYesThe requestId returned by car_send_request

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds genuine context beyond them by disclosing the lifecycle precondition that determines success or failure. It does not describe what happens to the underlying request or what a successful response looks like, which keeps it from a 5.

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?

Two short sentences, zero filler, and the valid-state condition is front-loaded before the exclusion clause. Every clause carries distinct information.

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?

For a single-parameter cancel operation with full annotation coverage and a fully described schema, the definition supplies the one thing that matters — the state gate. Only the post-cancellation effect (what state the request ends up in) is left implicit, which is minor.

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?

There is a single required parameter with 100% schema description coverage that already tells the agent requestId comes from car_send_request. The description adds no further detail on the identifier's format or origin, so the schema does the work and the baseline of 3 applies.

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?

The description states a specific verb (cancels) and resource (a request) and immediately scopes it with the lifecycle condition 'before it goes to a business (while it waits for the text code)'. An agent knows exactly what operation this performs and which state the target request must be in.

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

Usage Guidelines5/5

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

Both the when and the when-not are explicit: use it while the request is waiting for the text code, and it 'cannot be canceled here' once the request has gone to a business. That second clause actively steers the agent away from calling it in the wrong state.

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