Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Approve return

approve_return
Destructive

Approve a customer-requested return using the order ID and return ID, with an optional note saved to the return history.

Instructions

Approve a return the customer requested.

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": "approve_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

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds no behavioral detail beyond that: it does not explain irreversibility, required permissions, side effects, or what approval changes on the return.

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?

The description is a single front-loaded sentence with no wasted words. It is concise, but its brevity leaves little structure for an agent to work with beyond the basic action.

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

Completeness2/5

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

For a destructive mutation with no output schema, the description is too thin. It omits consequences of approval, permission requirements, and what the tool returns, leaving the agent without enough context to invoke it confidently.

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?

The description does not mention any of the three parameters. The schema documents returnId and note, but the required orderId parameter has no schema description and the description does not compensate for that 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?

The description states a specific verb and resource: "Approve" a "return," with the qualifier that the customer requested it. It is clear what the tool does, though it does not explicitly distinguish itself from siblings like reject_return or cancel_return.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. An agent must infer the routing from the name alone.

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