Schema | mcp-esim

mcp-esim

Describes the environment variables required to run the server.

Name	Required	Description	Default
`WCS_ESIM_API_BASE`	No	Override the API base URL	https://shop.worldcitisim.com/wp-json/esim/v1

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
esim_search_plansA	Search the WorldCitiSim eSIM catalog. Returns plans matching the given filters (country ISO code, region, desired days, desired GB). Plans have variations — each variation is one specific (days × GB × price) combo. The user picks one variation_id to buy.
esim_get_planA	Fetch the full detail of one plan by slug, including all variations (every days × GB permutation with its price).
esim_create_orderA	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.
esim_check_orderA	Poll an order's status. Returns `status: pending` while waiting for payment, `status: processing` or `completed` once paid, with `activation` data (ICCID, QR URL, install instructions).

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

A4.2/5.0

Scored 2026-06-19 22:50 across 4 tools

Disambiguation5/5

Each tool targets a distinct operation: searching plans, fetching plan details, creating orders, and checking order status. No overlap in purpose.

Naming Consistency5/5

All tools follow a consistent esim_verb_noun pattern (search_plans, get_plan, create_order, check_order).

Tool Count5/5

Four tools cover the eSIM purchase workflow adequately without being excessive or insufficient.

Completeness4/5

Core lifecycle (search, detail, order, status) is covered. Minor gaps like cancellation or order listing exist, but the main flow is complete.

ActivityInactive

ResponsivenessNo issues