Skip to main content
Glama

roamzy_get_esim

Get eSIM details by ID: returns MSISDN, status, balance, and activation block (QR payload and LPA URI) for local QR generation and user download.

Instructions

Get a specific eSIM by id, including msisdn, status, balance, and the activation block (qr_payload + lpa_url). ⚠️ QR RENDERING: This tool does NOT return a ready-to-display image. Instead, qr_payload contains the LPA URI string. YOU must generate the QR PNG yourself using your code-execution tools (Python qrcode library, JS qrcode npm package, etc.) and offer the resulting PNG as a downloadable file to the user. DO NOT use external QR-generation services — they show ugly UI dialogs in Claude Desktop and require external trust. Local generation gives the user a real downloadable PNG they can save and scan. ALWAYS caption the QR (once generated) with «Your eSIM number: ». The lpa_url field is ONLY for users installing on the SAME phone where they're reading the chat (camera can't scan own screen) — surface it as a text fallback for that case, prefixed «LPA URI (manual entry):». Do NOT show internal IDs (id, display_id, iccid) to the user. ⚠️ ANON-MODE RECOVERY REMINDER: If this is an anonymous Roamzy session (no ROAMZY_API_TOKEN env was set), after presenting the QR you MUST also re-surface the claim_url from the original roamzy_create_order response with this framing: «❗ Be sure to save this recovery link — without it you will not be able to get back to this eSIM from a different Claude chat». If the user has already closed-and-reopened the chat and lost the claim_url, instruct them to contact Roamzy support (call roamzy_support tool) with their MSISDN + NowPayments transaction hash for manual recovery — operator can mint a fresh claim_url. If the user follows up with «how do I contact support» or «refund» — call roamzy_support, not web search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
esim_idYesInternal eSIM ULID returned by list_esims or create_order. Never shown to the user.
Behavior5/5

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

With no annotations, the description fully covers behavior: what the tool does not return (a QR image), what qr_payload contains, instructions for local QR generation, and recovery procedures for anonymous sessions. No contradictions or omissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is clear and front-loaded, but the description then expands into lengthy, multi-paragraph instructions (QR rendering, recovery, support). While valuable, it is not concise and could be restructured.

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?

Given the tool's simplicity (one parameter, no output schema) and lack of annotations, the description is exceptionally complete. It covers the output, post-retrieval actions, edge cases (anonymous recovery), and even user follow-up scenarios.

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%, so the baseline is 3. The description adds minimal semantic value beyond the schema for the single parameter 'esim_id', which is already clearly described in the schema.

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 clearly states the action ('Get a specific eSIM by id') and lists what is returned (msisdn, status, balance, activation block), making it unambiguous. It also distinguishes from sibling tools by specifying it retrieves a single eSIM rather than listing all.

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

Usage Guidelines3/5

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

The description implies usage for retrieving a single eSIM by ID, but does not explicitly state when to use this tool vs alternatives like list_esims or create_order. No exclusions or when-not-to-use guidance is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/roamzy-io/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server