Skip to main content
Glama

esim_create_order

Create a pending eSIM order and get a Stripe payment link or Bitcoin payment details to complete the purchase.

Instructions

Create a pending order. With payment_method: "stripe" (default) you get back a payment_link_url — present it to the user to tap and pay on Stripe's hosted page. With payment_method: "btc" you get back a btc block (on-chain address + amount + QR data URI + expiry) — present the address and amount to the user to pay from any Bitcoin wallet; no redirect. If the user hasn't said how they want to pay, ask: card or Bitcoin. The eSIM QR code arrives at email within ~30 seconds of payment clearing. Use esim_check_order to poll status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesBuyer's email address. The eSIM QR code will be delivered here.
variation_idYesThe specific variation ID to buy (from esim_search_plans or esim_get_plan).
payment_methodNoHow the buyer pays. 'stripe' (default) → hosted card checkout, returns a payment_link_url. 'btc' → on-chain Bitcoin, returns a btc block (address + sats + QR) to show the user directly. BTC may be declined for small orders during network-fee spikes — the call then returns a btc_unavailable error and you should offer card instead.stripe
agent_sourceNoOptional: identifier for the calling agent (e.g. 'claude-code', 'cursor'). Used for our analytics; not seen by the buyer.
Behavior5/5

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

With no annotations, the description fully discloses behavior: creates pending order, returns different outputs per payment method, mentions possible btc_unavailable error, and states eSIM delivery time (~30 seconds). No hidden traits.

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?

The description is a single well-structured paragraph: concise yet comprehensive, with each sentence serving a purpose. No wasted words.

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 no output schema, the description covers return values for both payment methods, error case, and delivery timing. Suggests polling for status. Complete for the tool's role.

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. The description adds significant value by explaining payment_method behavior in detail (stripe returns payment_link_url, btc returns btc block with elements) and the btc_unavailable error, surpassing the schema's enums and descriptions.

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 'Create a pending order' and differentiates between payment methods, distinguishing it from sibling tools like esim_check_order (polling) and esim_search_plans (searching).

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?

Provides explicit guidance on when to use each payment method, instructs to ask user if they haven't specified payment method, and advises using esim_check_order for polling. Also covers the btc_unavailable error fallback.

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/isabellaliebgott/mcp-esim'

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