Skip to main content
Glama

Pay2GPT

Business: cancel an order

cancel_business_order
DestructiveIdempotent

For a company with a Pay2GPT business API key: cancel one of its orders that no ChatGPT account has been connected to yet; the credit goes back to the company's balance. A cancelled order cannot be reopened.

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_number": "<order_number>"
    },
    "name": "cancel_business_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_numberYesThe order number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructive=true and idempotent=true, so the safety profile is partly covered; the description still adds substantive context: the business API key prerequisite, the balance-refund behavior, and the fact that a cancelled order cannot be reopened. It stops short of describing the error path when the precondition is violated or what the response contains.

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?

One compact sentence front-loads the authorization context, then the action, the precondition, the financial effect, and the irreversibility note. Nothing is redundant or padded.

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 mutation with no output schema, the description covers authorization, eligibility, side effect, and irreversibility — enough to call it correctly. The only gap is the failure mode when the order already has a connected ChatGPT account, which an agent would only discover at runtime.

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 100% and the single order_number parameter is documented in the schema itself. The description only implies that the order must belong to the calling company, adding minimal meaning beyond the structured field — baseline 3 is appropriate.

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 ("cancel one of its orders") plus a scope qualifier (orders with no ChatGPT account connected yet) and the side effect (credit returns to the company balance). This is clearly distinguishable from get_business_order, list_business_orders, and place_business_orders 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 Guidelines4/5

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

Gives an explicit eligibility condition — the order must have no ChatGPT account connected yet — which effectively tells the agent when this call is valid and when it will fail. It also warns that cancellation is irreversible, but does not name a sibling alternative for orders that do have an account connected.

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