Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Update return tracking

update_return_tracking
Destructive

Set or correct the carrier and tracking number for a returned parcel, using the order and return IDs to update shipment details.

Instructions

Set or correct the carrier and tracking number of the parcel the customer sends back.

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": "update_return_tracking"
  }
}

Input Schema

NameRequiredDescriptionDefault
carrierNonull clears it
orderIdYes
returnIdYesThe return's id (get_order)
trackingNumberNonull clears it

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, and the schema already documents that null clears carrier and trackingNumber, so the description need not repeat either. What it does add is directional context (the customer's inbound parcel), which helps disambiguate the field meaning. It does not explain why the call is destructive (overwriting/clearing existing tracking), nor any state requirements or idempotency.

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 with no filler; the mutable fields appear immediately after the verb. Nothing in it is redundant with structured fields in a wasteful way.

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 definition is thin: it never says what the tool returns, what happens to a previously stored tracking number, or whether the return must be in a particular state. The core write intent is clear, but an agent would need to guess at the operational constraints.

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 75% and the description only names carrier and tracking number, which the schema already defines in more detail including the null-clears-it behavior. The orderId parameter has no schema description and gets no coverage from the description either. Baseline 3 is appropriate since the schema does most of the work.

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?

"Set or correct the carrier and tracking number of the parcel the customer sends back" gives a specific verb pair and the exact fields being written, and the inbound-parcel framing separates it from outbound shipment updates. It stops short of naming the sibling it competes with (e.g. update_shipment), so an agent must infer the boundary from the word "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 explicit when-to-use guidance: no statement of which return states this is legal in, no prerequisites such as the return existing or being approved, and no comparison to update_shipment. The word "correct" weakly implies fixing an already-recorded value, but nothing tells the agent when not to call it.

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