Skip to main content
Glama

order_cancel

Destructive

Cancel an unpaid order. A paid order has gone to the printer and can't be canceled.

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": "<order>"
    },
    "name": "order_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderYesOrder id (ord_…).
reasonNoWhy, for the record.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
summaryNo
warningsNo
next_actionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=false and openWorldHint=true, so the safety profile is carried by structured data. The description adds a genuinely non-derived fact: paid orders are past the printer and cancellation is impossible, which is the primary failure mode an agent must guard against. It does not explain whether a successful cancel is reversible or whether any refund side effect occurs, but given annotation coverage that omission is tolerable.

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 sentences, zero filler, and the usable precondition is front-loaded ahead of the failure condition. Nothing could be removed without losing 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 two-parameter destructive mutation with full schema coverage and an output schema (so return values need not be described), the definition covers the main decision point and the main failure mode. It stops short of covering retry semantics despite idempotentHint=false, which would matter for an agent recovering from a failed call.

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% for both parameters, so 'order' (ord_ id) and 'reason' are already documented in the schema. The description adds no format detail, no note on whether 'reason' is stored or surfaced to the customer, and no guidance on the string-or-number union type. Baseline 3 applies when the schema does the heavy lifting.

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 ('Cancel an unpaid order') with a scope qualifier that immediately separates it from order_purchase or order_update behavior. It stops short of naming any sibling or contrasting the cancel path with, say, ticket_create for already-printed orders, so differentiation is inferred rather than explicit.

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 an explicit when-to-use (unpaid orders) and an explicit when-not ('a paid order has gone to the printer and can't be canceled'), which is exactly the boundary an agent needs before attempting a destructive call. It does not point to an alternative route for the paid-order case, leaving the agent to guess whether ticket_create is the fallback.

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