Skip to main content
Glama

order_update

Change an order's file, options, quantity, address, deadline or budget. Content changes re-check and re-quote.

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": {
      "order": "<order>"
    },
    "name": "order_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
qtyNoNew quantity.
fileNoReplacement PDF, as an https URL it can be downloaded from (at most 32 MB), or the id (fil_…) of a file sent before.
foldNoFilter by fold.
noteNoYour note, kept on the order.
sizeNoFilter by size.
orderYesOrder id (ord_…).
sidesNoFilter by sides.
stockNoFilter by stock.
finishNoFilter by finish.
optionNoFilter by any option, as key=value. Repeatable.
pickupNoCollect from a pickup point instead of door delivery: a pkp_… id from `pickup-points`, "nearest", or "door" to switch back.
productNoChange the product.
ship_toNoDelivery address: a JSON file, inline JSON, or - for stdin. As an object: US {name, line1, city, state, postal_code}; Hong Kong {name, line1, district, area, phone, email, country: "HK"}.
max_totalNoBudget in the order's currency (USD, in the US and Hong Kong), e.g. 450; quotes above it are flagged.
deliver_byNoDeadline (YYYY-MM-DD); used to rank quotes, never a guarantee.
orientationNoFilter by orientation.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
summaryNo
warningsNo
next_actionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false. The description adds one genuinely non-obvious behavior beyond that: content changes trigger a re-check and re-quote, which signals a possible price change. However, the most important behavioral fact for a 16-param update tool is unstated – whether omitted fields are reset or left untouched (merge vs replace), and whether the re-quote must be confirmed via order_purchase.

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 with no filler, and the mutable-fields list is front-loaded. It is efficiently sized, though the second sentence is telegraphic enough that "re-check and re-quote" requires inference.

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?

An output schema exists and the annotations carry the safety profile, so the description need not explain return values. But for a tool with 16 parameters, a nested address object, and quote-affecting side effects, the two-sentence description leaves patch semantics and the re-quote confirmation path unexplained.

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 100%, so every parameter, including the nested ship_to and the pickup address form, is already documented in the schema; that alone justifies the baseline 3. The description's field list largely restates schema content, and it does not clarify which of the 16 fields count as "content" and therefore trigger the re-quote.

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 names a specific verb ("Change") and resource ("an order") and enumerates the mutable facets: file, options, quantity, address, deadline, budget. That lets an agent tell it apart from order_cancel/order_purchase without opening the schema, but it never contrasts itself with order_quote, the closest sibling for price-affecting changes.

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 only implied by the verb – an agent infers this is for modifying an existing order rather than creating one. There are no explicit when-to-use/when-not rules, no prerequisites (order must exist, must not be purchased/cancelled), and no pointer to order_quote for users who only want a price check before committing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources