Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Receive return

receive_return
Destructive

Records an incoming return parcel, capturing received units per line and restock quantities so stock is adjusted only for units returned to inventory.

Instructions

Record the return parcel as received: how many units of each line arrived and how many go back to stock. Stock is adjusted by the restocked units only.

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>",
      "lines": "<lines>"
    },
    "name": "receive_return"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
linesYes
orderIdYes
returnIdYesThe return's id (get_order)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true. The description adds one genuinely useful behavioral fact beyond them: stock is adjusted only by restocked units, not by all received units. It does not say whether the receipt is reversible, whether it affects refunds or return status, or what happens on a second call.

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 tight sentences, zero filler, with the core recording action and the stock-adjustment caveat front-loaded. Every clause carries information an agent needs.

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 destructive four-parameter mutation with no output schema, the description covers the key data semantics and side effect but omits preconditions, reversibility, and the resulting state change. Adequate to call correctly, thin for predicting consequences.

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 only 25%, but the description compensates for the two ambiguous quantities by mapping 'units of each line arrived' to receivedQuantity and 'go back to stock' to restockQuantity, clarifying that these are separate numbers. It says nothing about orderId, returnId, or note, leaving those to minimal schema hints.

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 ('Record the return parcel as received') and immediately names the two quantities captured per line. An agent can tell it is a receipt-recording mutation, though the description never contrasts it with siblings like complete_return or approve_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?

There is no when-to-use guidance, no precondition (e.g. whether the return must already be approved or in transit), and no named alternative for the other return-state transitions. Usage is only inferable from the verb.

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