Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Complete return

complete_return
Destructive

Closes a received return without issuing a refund, useful after store credit is given or inspection fails.

Instructions

Close a received return without a refund, e.g. after store credit or a failed inspection.

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": "complete_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.8/5.0
Behavior3/5

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

Annotations already flag this as a mutating, destructive operation, so the safety bar is lower. The description adds one genuinely useful fact beyond them — that no money moves on this path — and "close" implies a terminal state transition, but nothing is said about irreversibility, preconditions, or failure behavior.

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 that wastes no words; the scope constraint ("without a refund") arrives before the supporting examples.

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 three-parameter terminal action with no output schema and destructive annotations already in place, the description covers purpose and typical trigger conditions adequately. A note on required return state or what the caller should do on failure would close the remaining gap.

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%, with returnId already documented in the schema and note's persistence explained. The description contributes nothing about orderId versus returnId, so it neither compensates for the one undocumented parameter nor adds meaning beyond the schema — baseline 3 applies.

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?

"Close a received return without a refund" gives a specific verb plus resource and a negative scope qualifier that separates it from refund-oriented siblings. The examples ("after store credit or a failed inspection") sharpen the meaning further, though it never names an alternative tool explicitly.

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?

The description supplies concrete situations for use — store credit already issued, or a failed inspection — which is real when-to-use guidance rather than an implied context. It stops short of stating exclusions (e.g. what to call instead if the return is unreceived or a refund is still due).

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