Skip to main content
Glama

wait_for_order

Read-only

Wait for an order's status to leave inProgress, reading it every 15 seconds for up to about 45. Returns the order as get_order does, as soon as its status changes or once the wait is over; call again while it is still inProgress. Under heavy load it may return after a single read. Reports progress when the client asks for it.

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": {
      "id": "<id>"
    },
    "name": "wait_for_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOrder id, source Bitcoin txid, or source EVM tx hash

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only cover read-only and open-world safety; the description adds the operationally important traits: 15-second read interval, bounded ~45 window, retry loop semantics, and the caveat that heavy load may cause an early return after a single read. It also discloses that progress is reported when the client requests it.

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?

Three tight, front-loaded sentences with no filler, and the wait cadence leads. Minor blemish: 'up to about 45' omits the unit, which the reader must infer from the preceding '15 seconds'.

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 polling tool with no output schema, the definition covers cadence, timeout, return shape (delegated to get_order), retry behavior, and an edge case. The only gap is the ambiguous time unit and no guidance on whether a caller should prefer a manual get_order loop.

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?

The single `id` parameter is fully described in the schema (order id, Bitcoin txid, or EVM tx hash), and the description adds nothing further about it. With 100% schema coverage the schema carries this dimension, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb and resource plus the exact condition it waits on ('status to leave `inProgress`'), with polling cadence and a bounded wait window. It also distinguishes itself from the sibling get_order by noting it returns the order 'as `get_order` does' but only on change or timeout.

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?

Gives a clear usage loop: call again while status is still `inProgress`, and implicitly contrasts with a one-shot read via the get_order comparison. It stops short of an explicit 'if you want an immediate snapshot, use get_order instead' exclusion, so the alternative is inferable rather than stated.

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