Skip to main content
Glama

Cancel order

cancel_order
DestructiveIdempotent

Cancel a Fold order. Allowed only before the driver has picked up the bag — after pickup, items have to be returned unprocessed instead (the customer should call support). Requires the order code and the email used when scheduling. Returns the new state and confirms the saved card was not charged.

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

Input Schema

NameRequiredDescriptionDefault
emailNoEmail used when scheduling. Not needed when the customer has connected their Fold account.
reasonNoOptional reason — shown to ops, helps us improve.
orderCodeYesOrder code like FHL-RRKU92 or FOLD-K9ZGQ.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / email / description
      Previous value: -"Email used at booking. Not needed when the customer has connected their Fold account."New value: +"Email used when scheduling. Not needed when the customer has connected their Fold account."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructive=true and idempotent=true, but the description adds the critical operational constraint the annotations can't express: the pickup cutoff, the side effect on the bag (items must be returned unprocessed), the auth requirement, and the post-condition that the saved card was not charged. It also discloses the return shape (new state).

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 sentences, front-loaded with the action and its hard constraint, then the alternative, then inputs and return. Every clause carries operational information; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and a destructive mutation, the description still covers preconditions, auth, post-conditions, and the returned state, which is exactly what an agent needs to call it confidently and to explain the outcome to a customer.

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 schema already explains orderCode format, the optional reason, and the email-connected-account carve-out, so the description's parameter content is largely redundant. It does add that email identifies the scheduling record, but 'Requires the order code and the email' slightly overstates it, since email is not in the schema's required list.

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?

Opens with a specific verb+resource ('Cancel a Fold order') and immediately scopes it with the pickup cutoff. It is unmistakable against siblings like reschedule_order or list_my_orders, and it names the alternative path (return items unprocessed) when cancellation isn't allowed.

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 use condition (before driver pickup) and an explicit exclusion with the recommended alternative (after pickup, items must be returned unprocessed and the customer should call support). Nothing about when-to-use is left to inference.

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