Skip to main content
Glama

ALT eSIM

by com.altesim

get_qr_code

Fetch the eSIM QR code(s) for an order, to show the buyer directly. Pass the checkout_session_id from create_checkout. Returns a clear status: 'awaiting_payment' (buyer has NOT paid — tell them to pay), 'processing' (paid, eSIM still provisioning — retry in ~30s), 'ready' (returns the QR image(s) + ICCID(s) to display), 'expired', 'refunded', or 'failed'. Use the status to tell the buyer exactly what's happening — never assume payment succeeded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
checkout_session_idYesThe checkout_session_id from create_checkout (Stripe session id).

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, description fully discloses behavior: lists possible statuses ('awaiting_payment', 'processing', 'ready', 'expired', 'refunded', 'failed') and instructs agent to never assume payment succeeded. This is thorough for a simple tool.

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?

Description is concise, front-loaded with purpose, and each sentence adds meaningful information. No filler or redundancy.

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 has only one parameter and no output schema, the description effectively serves as the output schema by enumerating possible statuses and their implications. Covers all necessary guidance for correct invocation.

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 description coverage is 100%, but the description enhances the parameter by linking it to create_checkout, which adds workflow context. Without this, the parameter is self-explanatory, so baseline 3 + 1 for added value.

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?

Description clearly states 'Fetch the eSIM QR code(s) for an order' with a specific verb and resource. It distinguishes from siblings like create_checkout or get_esim_plan by focusing on QR retrieval linked to a checkout session.

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?

Explicitly says 'to show the buyer directly' and provides a prerequisite: 'Pass the checkout_session_id from create_checkout.' The status descriptions also guide the agent on how to interpret responses.

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

All ALT eSIM toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool has a clear, distinct role: listing destinations, searching plans, getting one plan, creating a checkout, and fetching QR/status. The create_checkout and get_qr_code tools are related but the descriptions clearly separate payment creation from fulfillment status.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: create_checkout, get_esim_plan, get_qr_code, list_destinations, search_esim_plans. This makes the API predictable and easy for an agent to navigate.

Tool Count5/5

Five tools is well-scoped for this server's purpose: discover destinations, search and inspect plans, create a payment checkout, and retrieve delivery/status information. Each tool earns its place with no redundancy.

Completeness5/5

The tool set covers the full eSIM purchase lifecycle: plan discovery, plan detail lookup, payment checkout creation, and QR code delivery with clear status handling. The get_qr_code status states cover waiting, processing, ready, expired, refunded, and failed, so agents can handle all outcome paths.

Resources