Quartermaster eSIM

Reissue the eSIM activation code

regenerate_activation

Get a fresh eSIM activation code (QR / LPA) for a delivered order whose code will not install. Use it after the troubleshoot steps fail, before opening a dispute. It works for any order of your principal (bought by any of its agents): it asks the supplier for a fresh code and returns the new delivery payload. Example: {order_id: "ord_..."}. The previous code may stop working. Not every supplier supports it (NOT_SUPPORTED_BY_SUPPLIER); then open a dispute with reason not_working.

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

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 already declare openWorldHint=true, idempotentHint=false, destructiveHint=false, and the description adds the key side effect the annotations do not convey: 'The previous code may stop working.' It also discloses the supplier dependency and the specific error code NOT_SUPPORTED_BY_SUPPLIER, though it does not describe timing or whether repeated calls issue yet another code.

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?

Front-loaded with the action, then sequencing, scope, side effect, and fallback in a compact sequence. No sentence is redundant with the name or with the schema descriptions.

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

Completeness4/5

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

For a mutation tool with no output schema, it covers preconditions, side effects, and the failure branch, but only says it 'returns the new delivery payload' without indicating the payload's shape. Auth needs are left to the schema. Overall adequate to call correctly.

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 baseline is 3, but the description adds real meaning: it clarifies that order_id can belong to any order of the calling principal ('bought by any of its agents'), which directly bears on how agent_id/principal_id/order_id interact. It also shows the expected order_id shape in the example.

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 ('Get a fresh eSIM activation code (QR / LPA)') plus the scoping condition ('for a delivered order whose code will not install'). It implicitly separates itself from troubleshoot ('after the troubleshoot steps fail') and from dispute handling, so an agent can pick it without reading sibling schemas.

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 ordering guidance: use it after troubleshoot fails and before opening a dispute. It also names the failure alternative ('NOT_SUPPORTED_BY_SUPPLIER; then open a dispute with reason not_working'), so both the happy path and the fallback are routed.

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.