Skip to main content
Glama

MeiSIM USA

Get activation QR

get_activation
Read-only

Get the eSIM install QR code, activation (LPA) string, and status for an order. Pass the order_id from purchase. Status is "ready" when the profile can be installed (after the customer pays).

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

Input Schema

NameRequiredDescriptionDefault
order_idYesThe order_id returned by purchase.

Output Schema

NameRequiredDescriptionDefault
statusYes
expires_atNo
activation_codeNo
qr_code_png_base64No
install_instructionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the payload shape and the semantics of the 'ready' status tied to payment. It does not discuss failure modes (e.g., what is returned before payment) or latency, so a 3 is fair.

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?

Two sentences, front-loaded with what is returned and followed by the one behavioral fact that matters (status semantics). No redundant or filler wording.

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-parameter read tool with an output schema, the description covers purpose, input provenance, and the meaning of the key return value. Nothing an agent needs to invoke it correctly is missing.

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 single parameter already documents 'The order_id returned by purchase,' which the description merely restates. Baseline 3 is appropriate since the schema carries the semantic load.

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 names a specific verb and resource ('Get the eSIM install QR code, activation (LPA) string, and status for an order'), so an agent knows exactly what it returns. It stops short of naming how it differs from siblings like get_order, but the enumerated payload largely does that work implicitly.

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 states the prerequisite explicitly: 'Pass the order_id from purchase,' establishing the correct call sequence, and explains that status is 'ready' only after the customer pays. It gives no explicit exclusions or alternatives, so it lands below a 5.

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.