Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Reject return

reject_return
Destructive

Rejects a customer-requested return by order and return ID, freeing its items for another return and optionally recording a note in the return history.

Instructions

Reject a return the customer requested; it frees its items for another return.

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": "reject_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.5/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, and the description adds a real consequence not in the annotations: rejecting frees the return's items for another return. It omits irreversibility/confirmation requirements and permission needs, but adds meaningful behavioral context beyond the hints.

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 compact sentence with the action front-loaded and the state-changing consequence immediately following; nothing is wasted.

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?

Adequate for a destructive mutation with annotations carrying the safety profile, but for a three-parameter irreversible operation it should say more about the optional note and the effect on order/return state after rejection.

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 explains none of the three parameters; schema coverage is only 67%, with orderId undescribed and the note parameter's purpose only lightly covered by the schema ('Saved in the return's history'). An agent gets no guidance on what orderId should be relative to the return.

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?

States a specific verb and resource ('Reject a return') and narrows the target to a customer-requested return, so an agent can distinguish it from approve_return or cancel_return by intent even though no sibling is named 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?

'The customer requested' implies the precondition (a pending/requested return), but there is no explicit when-to-use versus approve_return or cancel_return, and no note about when rejection is inappropriate.

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