Skip to main content
Glama

Order status

get_order
Read-only

An order and its payment details. With wait_seconds (up to 25) it answers as soon as the status changes: awaiting_payment, paid, delivering, delivered, refunded, expired.

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_id": "<order_id>"
    },
    "name": "get_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYes
wait_secondsNo
payer_addressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint=false, so the description carries the burden for behavior and does meaningful work: it discloses blocking long-poll semantics capped at 25 seconds and early return on status transition. It also enumerates the possible status values (awaiting_payment, paid, delivering, delivered, refunded, expired), which annotations cannot express.

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 sentences, no filler, with the payload described first and the blocking behavior second. The opening fragment's missing verb is a clarity cost rather than a verbosity problem.

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?

No output schema exists, and the description partially offsets that by naming the status values returned. For a read-only single-record fetch with a blocking mode, the main gaps are the unexplained payer_address parameter and the absence of not-found or timeout behavior.

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%, so the description must compensate. It explains wait_seconds well beyond the schema's numeric bounds by describing the long-poll trigger, and order_id is largely self-evident from its name and pattern, but payer_address is never mentioned in either the description or schema — an agent cannot tell what it is for or when to supply it.

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

Purpose3/5

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

The description opens with the noun phrase "An order and its payment details" — it names the resource and payload but never supplies a verb, so the agent must infer that the tool retrieves a single order. It is distinguishable from the sibling list_orders by the singular subject, but that distinction is inferential rather than stated.

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?

"With wait_seconds (up to 25) it answers as soon as the status changes" gives usable guidance on when to supply the long-poll parameter instead of polling in a loop. However, there is no guidance on when to call this versus list_orders, nor on what happens when no change occurs within the wait window.

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