Skip to main content
Glama

Pagetool

Cancel an unused pay link

cancel_client_checkout
DestructiveIdempotent

Retires a pay link that has NOT been paid (give code = the pcl_… part of pay_url, or site_key), so nobody can pay it. Nothing is charged. A link that was already paid cannot be cancelled here.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cancel_client_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoThe link code: the pcl_… part at the end of pay_url.
site_keyNoOr the site whose open pay link to cancel.

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 known. The description adds genuinely new behavioral context: the destruction is limited to invalidating the link, 'Nothing is charged', and the operation is a no-op for paid links. It does not say what the response contains or how an invalid/already-cancelled code is reported.

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 tight sentences, front-loaded with the verb, scope, and precondition, followed by the effect and the exclusion. No filler or restatement of the title.

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, non-open-world mutation with full schema coverage, annotations, and idempotency disclosed, the description covers everything needed to decide and call. The remaining gap is the return value / error behavior for an invalid or already-cancelled code, which is minor given there is no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaning the schema does not encode: 'code ... or site_key' communicates that these are alternatives for identifying the same target, which the flat optional schema leaves ambiguous. The 'pcl_… part of pay_url' hint is duplicated by the schema but reinforces the exact substring to supply.

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 ('Retires a pay link') plus a hard precondition ('that has NOT been paid') and the effect ('so nobody can pay it'). The closing 'A link that was already paid cannot be cancelled here' explicitly bounds the tool's scope, distinguishing it from payment/creation siblings like create_client_checkout and purchase_link.

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 a clear when-to-use condition (an unpaid, unused pay link) and an explicit when-not condition (already-paid links cannot be cancelled here). It stops short of naming what an agent should call instead for a paid link, so the exclusion is stated without a redirect.

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