Skip to main content
Glama

getOrderStatus

Get order status, tracking, timeline, and agent.messageToHuman. Prefer connected MCP (order-status island when host supports MCP Apps). After createCheckout/quickCheckout, wait ~60s then call this (and every 60s while open). Also call when the human asks for an update. No push webhook. Polling refreshes AliExpress tracking when available.

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

Input Schema

NameRequiredDescriptionDefault
orderIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose real behavior: polling cadence, absence of a push webhook, and that polling refreshes AliExpress tracking when available. It says nothing about authorization or scope requirements, what happens for an unknown orderId, or what the odd 'agent.messageToHuman' field actually is, so the picture is only partial.

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

Conciseness3/5

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

The purpose and the polling cadence are front-loaded, which is good. But two fragments — 'agent.messageToHuman' and 'Prefer connected MCP (order-status island when host supports MCP Apps)' — are cryptic jargon that cost the reader more than they convey, and the parenthetical could be dropped or rewritten.

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 one-parameter read tool with no output schema and no annotations, the description covers the when and the general shape of the return (status, tracking, timeline). It is incomplete on the identifier format, failure modes, and the host/MCP Apps caveat, all of which an agent would need to call this reliably.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is exactly one parameter, orderId, at 0% schema description coverage, and the description never mentions it — no format, no example, no statement of whether it is an internal ID, a supplier order reference, or a customer-facing number. Since the schema provides no help here, the description needed to compensate and does not.

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 opens with a specific verb and resource: 'Get order status, tracking, timeline, and agent.messageToHuman.' That tells an agent exactly what comes back. It does not distinguish itself from the admin-side siblings (adminGetOrder, adminGetTicket), and the parenthetical 'order-status island when host supports MCP Apps' is opaque, but the core purpose is unambiguous.

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?

It gives concrete triggers: after createCheckout/quickCheckout, wait ~60s, then call every 60s while the session is open, and also call when the human asks for an update. It also states 'No push webhook,' which implicitly explains why polling is required instead of an event-driven alternative. The only gap is that it never says when to prefer adminGetOrder or another sibling over this tool.

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