Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Edit order

edit_order
Destructive

Replace all line items on an existing order and automatically recompute totals. Use it to correct quantities, products, variants, or ad-hoc pricing in a single update.

Instructions

Replace an order's line items (full replace of the items array). Recomputes totals.

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>",
      "items": "<items>"
    },
    "name": "edit_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
orderIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / items / items / properties / price / description
      Previous value: -"Custom unit price in minor units (ad-hoc item)"New value: +"Custom unit price in minor units of the order's currency (ad-hoc item)"
    • addedInput schema / required
      Added value: +[
      +  "orderId",
      +  "items"
      +]
  2. First observedv0.73.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds meaningful context beyond them: the items array is fully replaced rather than merged, and totals are recomputed as a side effect. It does not describe error behavior or what happens to pricing/discounts attached to removed lines.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the destructive full-replace semantics. No wasted wording, though the parenthetical restates the same idea slightly.

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 mutation with no output schema, the description covers the essential risk (full replacement, totals recompute) but omits return information, validation constraints such as minItems=1, and any permission or state preconditions. Adequate but with clear gaps.

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 description coverage is 0% at the top level, but the nested item fields (name, price, recordId, variantSelections) carry their own descriptions. The description's key contribution is clarifying that 'items' is a full replacement array, though it says nothing about orderId or the ad-hoc vs. recordId line distinction.

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 ('Replace an order's line items') and clarifies the scope of the replacement. It is clearly distinct from sibling tools like update_order_details, though it does not name an alternative explicitly.

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: call this when the line items array must be replaced wholesale. There is no explicit when-not guidance, no mention of update_order_details for non-item fields, and no stated prerequisites such as the order needing to be open.

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