Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Update order details

update_order_details
Destructive

Updates selected order details—customer email, internal notes, PO number, delivery address, and custom fields—without changing omitted fields. Rejects country edits that alter frozen tax treatment.

Instructions

Update order metadata: customer email, internal notes, PO number, delivery address and custom order fields. Only provided fields change. A delivery address whose country would change the order's frozen tax treatment (taxTreatment in get_order, e.g. reverse_charge to standard) is refused (BAD_USER_INPUT, TAX_TREATMENT_CHANGED); cancel the order and place it again instead.

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

Input Schema

NameRequiredDescriptionDefault
notesNoInternal note, never shown to the buyer
orderIdYes
poNumberNoBuyer's purchase-order reference
customFieldsNoOrder custom fields by key (keys from the cart config's orderFields). A value sets the field, null removes it; keys not named stay as they are.
customerEmailNo
shippingAddressNoCorrect the delivery address; omitted leaves it unchanged

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / customFields
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Order custom fields by key (keys from the cart config's orderFields). A value sets the field, null removes it; keys not named stay as they are.",
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
    • removedInput schema / properties / trackingCarrier
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / trackingNumber
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / required
      Added value: +[
      +  "orderId"
      +]
  2. First observedv0.73.1

TDQS

A4.1/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 goes well beyond them by disclosing the patch contract ('only provided fields change') and a specific domain failure mode with its error code (BAD_USER_INPUT, TAX_TREATMENT_CHANGED) plus the recommended remedy. It still does not say whether the deletes/overwrites are recoverable or what a successful call returns, so it stops short of full behavioral disclosure.

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: field inventory first, the patch rule second, the refusal case and remedy last. Nothing is repeated and the failure mode is front-loaded before the agent wastes a call.

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 a destructive mutation with a nested address object and no output schema, the description covers scope, partial-update behavior, and the primary rejection condition. The remaining gap is placement relative to sibling mutation tools such as edit_order, which the description never addresses.

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?

Schema coverage is 67%, and the description compensates by naming every mutating field and stating partial-update semantics, which is the key fact an agent needs about optional parameters. It adds little per-field detail beyond the schema (e.g. no guidance on how a full shippingAddress object replaces the existing one), which keeps it from a 5.

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 states a specific verb and resource and enumerates exactly which metadata is mutable (customer email, notes, PO number, delivery address, custom fields). An agent can tell this apart from cancel_order or get_order, though it does not distinguish itself from the similarly named edit_order sibling.

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?

It gives a concrete instead-of path: when a delivery-address change would alter the frozen tax treatment, the tool is refused and the caller should cancel and re-place the order. That is an explicit exclusion with a named alternative flow. What is missing is general routing guidance versus edit_order or the other order-mutation siblings.

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