Skip to main content
Glama

Moqway

Cancel order

cancel_order
Destructive

Cancels an order and refunds the escrowed payment in full: any paid order before the supplier accepts, or an accepted order once it is past its ship deadline (order.overdue is true). Before that, an accepted order cannot be cancelled.

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_id": "<order_id>"
    },
    "name": "cancel_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
order_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is partly covered. The description adds real business context beyond that: the escrowed payment is refunded in full, and the refund is tied to a specific eligibility boundary. It stops short of saying whether a cancellation can be undone or what an ineligible attempt returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with the outcome front-loaded and the constraints trailing in a logical order. It is efficient, though the colon-and-parenthetical construction packs three distinct rules into one breath and takes a second read.

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 destructive, non-idempotent mutation with no output schema, the description supplies the two things an agent most needs: the eligibility gate and the financial consequence of calling it. Remaining gaps are the unexplained reason parameter and the failure mode when the order is not eligible.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden, and it only covers order_id indirectly through the eligibility rules and the order.overdue reference. The reason parameter (max 300 chars) is never mentioned, so the agent gets no guidance on what it is for or whether it is user-visible.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ("Cancels an order and refunds the escrowed payment in full") and then bounds the operation with concrete eligibility conditions. It never names a sibling, so differentiation is achieved by precondition rather than by routing, which keeps it short of a 5.

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 when-to-use rule: any paid order before supplier acceptance, or an accepted order that is past its ship deadline (order.overdue true). It also states a when-not condition ("an accepted order cannot be cancelled") but does not say what the agent should do instead in that case, leaving the alternative unstated.

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