Skip to main content
Glama

Cancel a cart

cancel_cart
Destructive

Permanently delete a cart by cart_id. Use when the customer abandons the session or wants to start over. Has no effect on any checkout or paid order already created from this cart. Irreversible, create a new cart to restart.

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": {
      "cart_id": "<cart_id>"
    },
    "name": "cancel_cart"
  }
}

Input Schema

NameRequiredDescriptionDefault
cart_idYes

Output Schema

NameRequiredDescriptionDefault
cart_idYes
cancelledYes

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 destructiveHint=true and readOnlyHint=false, so the description's value is in the extra detail it supplies: permanence, irreversibility, and that checkouts/orders derived from the cart are untouched. It stops short of stating failure behavior (e.g., cancelling an already-cancelled cart) or any auth/permission requirement.

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 destructive action, then trigger, then side-effect boundary, then the restart instruction. No filler or repetition 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 single-parameter destructive tool with an output schema and full annotation coverage, the description covers purpose, trigger, and blast radius, which is most of what an agent needs. The only real omission is error/prerequisite behavior.

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?

There is one parameter with 0% schema description coverage, so the description would need to carry the semantics; it only names cart_id without format, source, or validity details. It does implicitly clarify that the id refers to a cart rather than a checkout, which is a small but real addition.

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?

"Permanently delete a cart by cart_id" is a specific verb plus resource, and the following sentence scopes it away from checkouts and paid orders, so an agent can distinguish it from cancel_checkout or update_cart without opening their schemas.

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?

It gives an explicit trigger ("customer abandons the session or wants to start over") and a boundary condition (no effect on existing checkouts or paid orders). It does not name a specific alternative tool to use instead when a checkout is involved, which keeps it short of a 5.

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