Quartermaster eSIM

Order status

order_status

Read-only

Look up one order. Use it after purchase to confirm delivery and read the activation code, whenever a purchase returned status processing, and to check data usage. Read-only. Example: {order_id: "ord_..."}. Returns the current order state, eSIM delivery payload, activation and data usage from the supplier, receipts, and the latest disputes (disputes_total counts all). Any agent of the order's principal may call it (and regenerate_activation and request_refund) for the order; other principals get ORDER_NOT_FOUND.

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": "order_status"
  }
}

Input Schema

Name	Required	Description
`agent_id`	No	Your agent id (or X-Agent-Id header)
`order_id`	Yes	Order id from purchase (order.order_id) or from an earlier order_status call
`agent_key`	No	Secret returned by register_agent (or X-Agent-Key header)
`principal_id`	No	The principal you act for (or X-Principal-Id header)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

addedInput schema / properties / order_id / description

Added value: +"Order id from purchase (order.order_id) or from an earlier order_status call"

Changed4 schema fields changedNov 4, 2026
- addedInput schema / properties / agent_id / pattern
```
Added value: +"^[A-Za-z0-9._:-]{3,128}$"
```
- addedInput schema / properties / agent_key / maxLength
```
Added value: +256
```
- addedInput schema / properties / order_id / maxLength
```
Added value: +128
```
- addedInput schema / properties / principal_id / pattern
```
Added value: +"^[A-Za-z0-9._:@-]{3,128}$"
```
First observedNov 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations only declare readOnlyHint, and the description goes well beyond that by disclosing the authorization model ('Any agent of the order's principal may call it... other principals get ORDER_NOT_FOUND') and the exact error code returned on unauthorized access. It also previews the return payload including that disputes_total counts all disputes; it does repeat 'Read-only' from the annotation but that is a minor redundancy rather than a gap.

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 and use cases are front-loaded, and each sentence carries concrete information about triggers, return contents, or access rules. The list-style density and the redundant 'Read-only' phrase cost it some crispness, but there is no filler prose.

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?

For a single-order read with no output schema, the description covers usage triggers, authorization boundaries, error behavior, and the main components of the response (state, eSIM payload, activation, data usage, receipts, disputes). Nothing an agent needs in order to call it correctly or interpret a failure is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: an example order_id literal format ('ord_...') and authorization semantics tied to principal_id. The agent_key/agent_id parameters are left to the schema and header alternatives, which is acceptable given the schema handles them.

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?

The description opens with a specific verb and resource ('Look up one order') and immediately scopes it to a single order, which distinguishes it from list-style siblings like get_quote, get_wallet, and purchase. An agent can tell it retrieves order state rather than creating or modifying anything.

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?

It enumerates concrete triggers: after purchase to confirm delivery, to read the activation code, when a purchase returned status 'processing', and to check data usage. It also names related tools (regenerate_activation, request_refund) that share the same authorization scope, giving the agent a clear map of adjacent actions.

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

All Quartermaster eSIM 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.