Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Cancel order

cancel_order
Destructive

Cancel an order using only its order ID. If the user gives a reason, record it in the order's notes first with update_order_details, then cancel.

Instructions

Cancel an order. Takes only the order id - there is no reason field; when the user gives a reason, record it in the order's notes with update_order_details first.

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

Input Schema

NameRequiredDescriptionDefault
orderIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / required
      Added value: +[
      +  "orderId"
      +]
  2. First observedv0.73.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is established structurally. The description contributes the non-obvious fact that no reason is accepted and that reason capture must happen through a separate tool beforehand, but it says nothing about reversibility, resulting order state, or side effects on related records.

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 short sentences, action first, constraint and prerequisite second. Every clause eliminates a plausible agent mistake, and there is no redundant restatement of the title or annotations.

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 annotations covering the safety profile and no output schema, the description supplies both the input constraint and the pre-step workflow an agent needs. It could be more complete by noting whether cancellation is reversible or what state the order ends in.

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 description coverage is 0%, so the description must carry the load; it does so by stating the tool takes only the order id and explicitly ruling out a reason field, which prevents the common error of hunting for a missing parameter. It does not describe the id format or validation (minLength 1), a minor remaining gap.

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?

"Cancel an order" states a specific verb and resource, and the follow-up sentence pins down the exact input (the order id alone). It does not explicitly distinguish itself from close_order or cancel_return, so sibling differentiation is left to inference, but the core action is unmistakable.

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 a concrete conditional workflow: if the user supplies a reason, call update_order_details first to store it in the order's notes, then cancel. That is real when-to-do-something-else guidance naming the alternative tool, though there are no exclusions covering cases like already-shipped orders or open returns.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools