Skip to main content
Glama

Cancel an unpaid order

cancel_order
Destructive

USE THIS when the human changes their mind before paying. Cancels an unpaid order so the payment link stops working. A paid order cannot be cancelled here; use start_return.

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": {
      "order_id": "<order_id>"
    },
    "name": "cancel_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYes

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 and readOnlyHint=false, but the description adds real context beyond them: the concrete side effect (the payment link is invalidated) and the precondition that only unpaid orders qualify. It stops short of saying what is returned or whether a repeat call on an already-cancelled order errors, which would matter for a destructive mutation.

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?

Three short sentences: trigger first, effect second, exclusion plus alternative last. Every sentence carries distinct information and nothing is restated from the title or schema.

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 one-parameter destructive mutation with annotations covering the safety profile, the description covers the trigger, the precondition, the effect, and the escape hatch. Gaps are limited to return/error behavior on repeat or already-cancelled calls, which is a minor omission at this complexity.

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?

With one parameter and 0% schema description coverage, the description carries the burden of explaining order_id, and it does not — no format, source, or example is given. The single identifier is self-explanatory in name, so the omission is mild, but no meaning is added beyond the bare schema.

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?

States a specific verb and resource ('Cancels an unpaid order') plus the concrete observable effect ('the payment link stops working'), and explicitly excludes a related case by naming the sibling start_return. An agent can distinguish this from start_return and create_order without opening any schema.

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?

Gives an explicit trigger ('when the human changes their mind before paying'), an explicit exclusion ('A paid order cannot be cancelled here'), and the alternative to use instead ('use start_return'). Both the when and the when-not are stated, not inferred.

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