Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Refund order

refund_order
Destructive

Refund an order in full or partially by passing an amount in minor currency units, with a reference for the receipt.

Instructions

Refund an order. Omit amount for a full refund; pass amount (minor units of the order's currency) for a partial refund.

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>",
      "reference": "<reference>"
    },
    "name": "refund_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountNoPartial refund amount in minor units of the order's currency; omit for full refund
orderIdYes
referenceYesRefund reference / receipt id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / amount / description
      Previous value: -"Partial refund amount in minor units; omit for full refund"New value: +"Partial refund amount in minor units of the order's currency; omit for full refund"
    • addedInput schema / required
      Added value: +[
      +  "orderId",
      +  "reference"
      +]
  2. First observedv0.73.1

TDQS

A3.5/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 agent knows this is a state-changing operation. The description adds the meaningful full-vs-partial distinction, but says nothing about irreversibility, whether a partial refund can exceed the order total, or what the required 'reference' is used for.

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 sentences, zero filler, and the full-refund default is stated before the partial-refund variant. The reader gets the core behavior in the first clause.

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

Completeness3/5

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

For a three-parameter destructive mutation with no output schema, the definition covers the primary mode split but leaves gaps: no description of what a successful refund returns, no constraint linking amount to the order total, and no mention of why reference is mandatory. Adequate but not complete.

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 description coverage is 67%, so the schema already explains amount and reference. The description restates the amount semantics (minor units, omit for full) without adding new information, and leaves orderId entirely undocumented in both places.

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+resource ('Refund an order') and immediately distinguishes the two modes of operation (full vs partial). It does not name or contrast with any sibling tool, such as refund_return or cancel_order, so an agent still has to infer which sibling handles returns versus refunds.

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?

It clearly explains when to omit amount and when to pass it, which is useful mode-selection guidance. However, there is no guidance on when to use refund_order versus cancel_order, refund_return, or close_order, and no stated prerequisites or exclusions, so tool-level selection 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.

Deploy Server

Other Tools