Skip to main content
Glama

order_wait

Read-onlyIdempotent

Wait until the order reaches a state. Exits 9 on timeout; call again to keep waiting.

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_wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
forNoTarget: quoted, change, paid, accepted, shipped, ready_for_pickup, delivered.
orderYesOrder id (ord_…).
timeoutNoSeconds to wait, at most 120 (default 25).

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
summaryNo
warningsNo
next_actionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, but the description adds real behavior: the wait aborts with exit 9 on timeout and the caller should re-invoke to continue. That retry semantics detail is not derivable from the annotations or schema and is the key operational fact an agent needs.

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 short sentences, the core action front-loaded, followed by the failure/retry rule. No filler or redundancy.

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?

With an output schema present, the description need not explain return values, and annotations cover the safety profile. Timeout behavior and continuation are covered; the only modest gap is that it does not clarify whether the call blocks or how partial states are handled.

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 100%, with the target states, order id format, and the 120-second cap already documented in the schema. The description adds only the implicit link between the timeout and re-calling, so it neither compensates for nor extends the schema meaningfully.

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 ('Wait until the order reaches a state'), which is clearly distinct from read-oriented siblings like order_show or order_list. It does not explicitly name a sibling it replaces, so it stops short of 5.

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?

'Call again to keep waiting' gives concrete guidance for the timeout path, and the target states are enumerated in the schema. However, it never says when to prefer this over polling order_show or order_events, so the when-to-use decision is only implied.

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