Skip to main content
Glama

roamzy_get_esim

Retrieve eSIM details by ID including MSISDN, status, and balance. Obtain LPA URI string for local QR code generation.

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 «Ваш номер eSIM: » / «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: «❗ Не забудь сохранить ссылку восстановления — без неё ты не вернёшься к этой eSIM из другого Claude-чата». 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 discloses behavior: it returns data (not an image), specifies what not to show to users (internal IDs), and gives detailed post-retrieval instructions for QR generation and anonymous recovery. This is comprehensive disclosure.

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 description is verbose (150+ words) with extensive procedural instructions. While every sentence adds value, the length reduces conciseness. The first sentence clearly states purpose, but the overall structure could be tighter.

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?

Given no output schema and one parameter, the description is complete in covering returned fields and post-processing steps (QR, recovery). It lacks error handling details (e.g., invalid ID), but the extensive behavioral guidance compensates.

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 schema already describes esim_id's source and usage. The description adds no extra information about the parameter beyond what the schema provides, so baseline of 3 is appropriate.

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 tool retrieves a specific eSIM by ID, listing exact fields returned (msisdn, status, balance, activation block). It distinguishes from sibling tools like roamzy_list_esims (which lists all eSIMs) and roamzy_create_order.

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?

The description provides clear context: use when you have an esim_id to get details. It implicitly tells when to use (when you have an ID) and includes post-retrieval guidance, but does not explicitly exclude alternatives or compare to siblings.

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