Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Update shipment

update_shipment
Destructive

Change a parcel's delivery status or correct its tracking details using order and shipment IDs; only supplied fields are modified, leaving stored values unchanged.

Instructions

Change a parcel's delivery status or correct its tracking. Only provided fields change; sending the stored values changes nothing.

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>",
      "shipmentId": "<shipmentId>"
    },
    "name": "update_shipment"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoSaved in the parcel's status history
statusNo
carrierNonull clears it
orderIdYes
labelUrlNonull clears it
shipmentIdYesThe parcel's id, from get_order
trackingUrlNonull clears it
trackingNumberNonull clears it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already disclose that this is a mutating, destructive operation, so the bar is lower. The description adds genuinely useful behavior the annotations do not cover: the write is a partial patch, so only supplied fields change, and resending stored values is a no-op. It still says nothing about side effects such as customer notifications or whether status transitions are validated.

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 sentences, each pulling weight: the first says what changes, the second states the partial-update contract. It is front-loaded with no filler.

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 an 8-parameter destructive mutation with no output schema, the definition covers the update contract but not the risk surface: no mention of irreversible state effects, permission needs, or what the response contains. The required orderId and shipmentId are documented in the schema, so that gap is minor.

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%, which is the baseline 3. The description reinforces patch semantics ('only provided fields change'), which clarifies how the six optional parameters behave, but leaves field-specific meanings, including null clearing and the note being written to status history, to the schema.

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: change a parcel's delivery status or correct its tracking. That is enough to separate it from create_shipment and cancel_order, but 'correct its tracking' slightly overlaps with the sibling update_return_tracking, and the description does not draw that boundary.

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?

Usage is implied rather than stated: it applies when a status change or tracking correction is needed. There is no explicit when-not guidance, no prerequisites, and no named alternative (for example cancel_order versus setting status to 'canceled').

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