Xpress Flow Systems

get_order_status

Read-only

Look up an order made with create_domain_order, create_esim_order or create_proxy_order. Statuses: pending_payment (waiting for payment; for a phone-number order held for an ID check, payment_url appears once approved and nothing is charged before that), paid, activating (paid and being prepared; details arrive by email and on the order page, and they can ask for a full refund before delivery), delivered, failed, refunded. Delivered orders carry the eSIM activation details or the proxy lines. For domains, delivered means registered.

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": {
      "reference": "<reference>",
      "token": "<token>"
    },
    "name": "get_order_status"
  }
}

Input Schema

Name	Required	Description	Default
`token`	Yes	The access token: the last part of status_url.
`reference`	Yes	Order reference such as XF-7K3Q9DFA.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=true, and the description adds substantial behavior beyond that: the full status lifecycle, the fact that nothing is charged before ID approval, that payment_url appears only once approved, that activation details arrive by email and on the order page, and that a full refund is possible before delivery. It also disambiguates "delivered" per product type (eSIM activation details, proxy lines, domain registration), which no structured field conveys.

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?

Purpose is front-loaded in the first clause, followed by a compact status enumeration and product-specific delivery semantics; no sentence is filler. The status list with parenthetical caveats is dense but each parenthetical carries distinct decision-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of explaining return semantics and does so: it enumerates every status value, explains what each means operationally, and states what a delivered order contains for each product line. An agent knows both what to expect and how to interpret it.

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% and the schema already explains both the token ("last part of status_url") and the reference format ("XF-7K3Q9DFA"). The description adds no further parameter meaning, so the baseline of 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?

Opens with a specific verb+resource ("Look up an order") and names the three sibling creation tools whose output it resolves. An agent can distinguish it from get_cart_status and the create_* tools without opening any schema.

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?

Scope is well bounded: it applies to orders made via create_domain_order, create_esim_order or create_proxy_order, which implicitly excludes cart lookups handled by get_cart_status. It stops short of an explicit "use get_cart_status for carts" routing statement, so the exclusion is inferred rather than stated.

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

All Xpress Flow Systems tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?