Skip to main content
Glama

Cancel checkout

cancel_checkout
Destructive

Abort an unpaid checkout and release its checkout_id. Use if the customer changes their mind after create_checkout but before completing payment. Has no effect on orders already confirmed by webhook. To restart, create a new cart and checkout from scratch.

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": {
      "checkout_id": "<checkout_id>"
    },
    "name": "cancel_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkout_idYes

Output Schema

NameRequiredDescriptionDefault
statusYes
checkout_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, so the description's added value is the boundary condition: no effect on webhook-confirmed orders, and a cancelled checkout cannot be resumed – a new cart and checkout are required. It does not cover failure modes such as an already-expired or already-cancelled checkout, or auth prerequisites.

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?

Four short sentences, front-loaded with the action and the effect, then the usage boundary, then the recovery path. No sentence restates the title or wastes words.

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?

An output schema exists, so return values need not be explained, and the lifeycle constraints (unpaid only, confirmed orders unaffected, restart-from-scratch) cover the main decision an agent faces. Idempotency and behavior on an already-cancelled or expired checkout are the remaining gaps.

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 coverage is 0%, but there is only one required parameter and the description names it and states the result of passing it ('release its checkout_id'). Beyond that it adds no format or validity detail, so the single-parameter schema still carries most of the burden.

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 ('Abort an unpaid checkout') plus the side effect ('release its checkout_id'), which is enough to distinguish it from create_checkout, cancel_cart, and complete_checkout in the sibling list.

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 ('customer changes their mind after create_checkout but before completing payment'), an exclusion ('no effect on orders already confirmed by webhook'), and a recovery path ('create a new cart and checkout from scratch'). An agent knows when to pick this and what to do instead if it is too late.

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