Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Create shipment

create_shipment

Add a parcel with items, carrier, tracking, and status to an order to mark fulfillment and update delivery status.

Instructions

Add a parcel to an order: the items it carries, carrier, tracking and status. This is also how an order is marked fulfilled. The order's fulfillment and delivery status follow its parcels; a pending parcel (no label yet) fulfils 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>"
    },
    "name": "create_shipment"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoSaved in the parcel's status history
itemsNoLines and quantities in this parcel. Omit to send every unit not yet in a shipment
statusNoDefaults to label_purchased with a tracking number, else pending. Use delivered for an order handed over in person, in_transit for one sent without tracking
carrierNo
orderIdYes
labelUrlNohttp(s) link to the printable shipping label
trackingUrlNohttp(s) link to track the parcel
trackingNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, which is a bare safety profile. The description adds genuinely consequential behavior: creating a shipment is the mechanism that marks an order fulfilled, and order status is derived from parcel status. The caveat that a pending parcel (no label) fulfils nothing is exactly the kind of side-effect nuance annotations cannot convey.

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?

Three tight sentences, front-loaded with the core action, followed by the less obvious fulfillment semantics and then the edge case. No filler, and each sentence contributes a distinct fact.

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

Completeness4/5

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

For an 8-parameter mutation tool with no output schema, the description supplies the crucial domain semantics (fulfillment linkage, pending-parcel behavior) an agent needs to call it correctly. It leaves return-value expectations unstated, though the derived-status explanation largely compensates.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

At 63% schema coverage, the schema documents most fields (items, status, note, labelUrl, trackingUrl), but the description reinforces what the parcel carries and ties status to fulfillment outcomes. It adds meaning beyond the schema by explaining the pending-without-label case. Minor gaps remain for carrier and label fields, but the description complements the schema well.

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 opens with a concrete verb+resource ("Add a parcel to an order") and enumerates the constituent data (items, carrier, tracking, status). It also discloses a second, non-obvious purpose — marking the order fulfilled — which an agent could not infer from the name alone. It does not explicitly contrast itself with the sibling update_shipment, keeping it just short of a 5.

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

Usage Guidelines4/5

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

"This is also how an order is marked fulfilled" gives a clear contextual signal for when to reach for this tool rather than a generic order-update. The closing sentence on pending parcels further clarifies the fulfillment condition. It stops short of naming alternatives or exclusions, so 4 rather than 5.

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