Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Cancel return

cancel_return
Destructive

Cancel a requested or approved return that has not yet been refunded, using the order ID and return ID. Stops further processing of the return in your Cmssy workspace.

Instructions

Cancel a requested or approved return that has not been refunded.

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>",
      "returnId": "<returnId>"
    },
    "name": "cancel_return"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoSaved in the return's history
orderIdYes
returnIdYesThe return's id (get_order)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation risk is surfaced structurally. The description adds the useful eligibility precondition, but says nothing about what cancellation does to the return record, whether it is reversible, or whether refunds/inventory are affected.

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?

A single front-loaded sentence with the state constraint attached directly to the action; there is no filler, hedging, or redundant restatement 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 3-parameter, non-read-only tool with no output schema and only the destructive flag as annotation, the description covers what it cancels and the state gate. What remains thin is the post-condition — the resulting state of the return — but the essentials for correct invocation are present.

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 67%: returnId and note are documented inline, while orderId has no description. The tool description adds no parameter-level meaning beyond the schema, so it neither compensates for the undocumented orderId nor risks contradicting it.

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 gives a specific verb ('Cancel') and resource ('return') and constrains it to returns in 'requested or approved' state that are 'not refunded'. That scope narrows it against siblings like refund_return or complete_return, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Eligibility is implied via the state qualifier ('requested or approved... not refunded'), which tells an agent when the call is valid. There is no explicit when-not guidance and no mention of reject_return or cancel_order as the preferred route in adjacent situations.

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