SimFuse eSIM Storefront

Get order status

get-order-status

Read-onlyIdempotent

Check an eSIM order after payment: whether it completed and whether its eSIMs have been provisioned yet. Identified by the order id together with the email that bought it, both of which are on the buyer's confirmation email. Provisioning usually finishes within a minute of payment, so an order that is paid but lists no eSIMs yet is normal: check again shortly. Once an eSIM is listed, use get-esim-activation to fetch its QR code and install details.

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>",
      "email": "<email>"
    },
    "name": "get-order-status"
  }
}

Input Schema

Name	Required	Description	Default
`email`	Yes	The email address the order was bought with. Required: the order id alone does not identify a buyer.
`order_id`	Yes	The order id from the buyer's confirmation email or order page.

Output Schema

Name	Required	Description
`note`	Yes	What to do next, given the list above.
`esims`	Yes	Every eSIM provisioned on this order. EMPTY while provisioning is still in flight, which is normal for the first minute after payment and never means the order failed.
`status`	Yes	Order state, e.g. "completed" or "pending". "completed" is about the eSIM having provisioned, not about the money.
`order_id`	Yes	The order, echoed back.
`placed_at`	Yes	When the order was created, ISO 8601. Null on the rare row that has no timestamp.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world semantics, so the bar is lower. The description still adds meaningful behavioral context the annotations cannot convey: eventual consistency (provisioning usually finishes within a minute) and the instruction that an empty eSIM list right after payment is normal and should be re-checked shortly.

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?

Four tight sentences, each doing work: purpose, identification, timing caveat, next step. The core purpose is front-loaded and the routing hint comes last where it belongs.

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?

An output schema exists, so return values need not be explained. Between the description's lifecycle framing, retry guidance, and next-step routing, an agent has everything needed to call this correctly and interpret an empty result.

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 100%, so baseline is 3. The description reinforces that both order id and email are needed and explains the email's role (the order id alone does not identify a buyer), but adds little beyond what the schema fields already state.

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 specific verb and resource (check an eSIM order) and names exactly what it reports: completion status and whether eSIMs have been provisioned. It is clearly distinguishable from siblings like get-esim-activation, which the description positions as the downstream step.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use context (after payment), the identifiers required and where to find them (buyer's confirmation email), guidance for the ambiguous 'paid but no eSIMs yet' case, and an explicit hand-off to get-esim-activation once an eSIM is listed.

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

All SimFuse eSIM Storefront 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?