Skip to main content
Glama

Siima eSIM

by online.siima
OverviewDiscussionsAdmin

Server Details

Search travel eSIM plans for 150+ countries and buy via Stripe link; eSIM QR delivered by email.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
99.9% over 57 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

A4.2/5.0

Scored across 5 tools

Disambiguation4/5

The purchase tool (create_checkout_link) and the single-plan lookup (get_esim_plan) are clearly distinct. However, list_destinations, list_regions, and search_esim_plans all browse destination/coverage data, and search_esim_plans can filter by country or region, so boundaries overlap somewhat—though the descriptions explain when to use each.

Naming Consistency5/5

All names follow a consistent snake_case verb_noun pattern (create_checkout_link, get_esim_plan, list_destinations, list_regions, search_esim_plans). Verb choices are predictable and readable throughout.

Tool Count5/5

Five tools is well-scoped for an eSIM discovery-plus-purchase flow. Each tool has a clear role: browse by country, browse by region, search/filter, fetch details, and generate a checkout link.

Completeness4/5

The discovery-to-purchase lifecycle is fully covered, with no account required. Minor gap: no tool to check order/payment status or retrieve an existing eSIM/order, though the email-delivery design largely makes that unnecessary.

Available Tools

5 tools
get_esim_planGet eSIM plan detailsAInspect

Fetch full details of a single Siima eSIM plan by its id (from search_esim_plans). To buy: call create_checkout_link with the plan id, give the returned URL to the user. They confirm their email with a 6-digit code and pay there; nothing is ordered until they do. After payment they are emailed a link to their eSIM; opening it on their phone gives a one-tap install, the QR code and manual codes. No account needed.

ParametersJSON Schema
NameRequiredDescriptionDefault
plan_idYesPlan id returned by search_esim_plans
currencyNoCurrency for prices: "usd", "eur", or "gbp". Defaults to "usd".usd

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: no ordering occurs until email confirmation and no account is needed. However, it spends most of its words on the downstream purchase flow rather than on this call's own behavior (e.g. that it is a read-only lookup or what 'full details' encloses).

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 definition is front-loaded with the core purpose, which is good, but then devotes four sentences to the checkout, payment, and install journey that logically belongs to create_checkout_link. That detail is helpful user-facing context but not this tool's contract, diluting a description that should be tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A read-only lookup with no output schema and no annotations needs the description to convey what comes back; 'full details' is vague and return fields are never hinted at. The auth-free nature ('No account needed') is covered, so the gap is moderate rather than severe.

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 description coverage is 100%, so both plan_id and the currency enum are already documented in the schema. The description only confirms the id's provenance ('from search_esim_plans') and adds nothing about the currency parameter, so the baseline 3 applies.

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?

States a specific verb and resource ('Fetch full details of a single Siima eSIM plan'), scopes it to one plan by id, and names the sibling (search_esim_plans) that produces that id. An agent can confidently distinguish it from search_esim_plans and create_checkout_link.

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?

Explicitly routes the agent: the id comes from search_esim_plans, and buying is done via create_checkout_link, not this tool. It gives clear upstream/downstream context but stops short of stating when this tool should be skipped or contrasting it against list_destinations/list_regions.

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

list_destinationsList covered destinationsAInspect

List all countries Siima sells a single-country eSIM plan for, with plan counts and the cheapest total price per country. Country codes are ISO 3166-1 alpha-2. Counts and prices cover country plans only, so they stay comparable — many more countries are reachable via multi-country plans; call list_regions for those.

ParametersJSON Schema
NameRequiredDescriptionDefault
currencyNoCurrency for prices: "usd", "eur", or "gbp". Defaults to "usd".usd

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that counts and prices are limited to country plans for comparability, and notes that many more countries are reachable via multi-country plans, which is a meaningful scoping constraint. It doesn't mention pagination or ordering, but for a simple list tool, this is adequately transparent.

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?

Two sentences, front-loaded with the primary purpose and followed by a necessary scope caveat. No wasted words; every clause adds value.

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, the description does a good job indicating what the response contains (countries, counts, prices) and the ISO code format. It also explains the scope limitation clearly. Minor gaps exist around ordering and exact response shape, but for a low-complexity list tool this is sufficiently complete.

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?

The schema already fully documents the currency parameter, including enum values, default, and description. The tool description adds no additional semantic detail about the parameter, but schema coverage is 100%, so the 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 lists countries with single-country eSIM plans, including plan counts and cheapest total price. It specifies the ISO 3166-1 alpha-2 format for country codes and distinguishes itself from sibling list_regions by explicitly noting the scope limitation to single-country plans.

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?

It explicitly explains when to use this tool (for single-country plans) and directs users to list_regions for multi-country plans. This provides clear when-to-use vs. alternative guidance, satisfying the highest bar for this dimension.

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

list_regionsList regional & worldwide coverage areasAInspect

List every multi-country coverage area Siima sells — regional areas such as "Europe+", "South East Asia" or "CENAM", and worldwide plans — with the countries every plan in it covers, how many plans it has, and its cheapest total price. Use this for a trip crossing several countries: pick a coverage area whose countries list contains the whole itinerary, then pass its name as coverage to search_esim_plans. countries_on_some_plans lists countries only some of the area's plans include — if the itinerary needs one, confirm the chosen plan covers it with get_esim_plan before buying. For a single-country trip use list_destinations instead.

ParametersJSON Schema
NameRequiredDescriptionDefault
countryNoOnly return coverage areas that include this ISO 3166-1 alpha-2 country, e.g. "IT"
currencyNoCurrency for prices: "usd", "eur", or "gbp". Defaults to "usd".usd

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose the return shape (countries per area, plan count, cheapest total price) plus the important semantic caveat that countries_on_some_plans may not be covered by every plan. It stops short of stating pagination, auth, or rate-limit behavior, but the substantive behavioral risks are covered.

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

Conciseness4/5

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

Front-loaded with purpose and examples, then workflow, then the sibling disambiguation last. Dense but nearly every clause carries actionable information; the country-example list is slightly verbose but aids recognition.

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?

With no output schema and no annotations, the description must explain returns and usage, and it does both: it enumerates the returned fields, clarifies the countries vs countries_on_some_plans distinction, and links to the downstream tools needed to act on the result.

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 description coverage is 100%, so both parameters (country, currency) are already documented in the schema and the description adds nothing about them. The references to `coverage` and `countries` belong to sibling tools, not this tool's inputs. Baseline 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?

States a specific verb and resource ('List every multi-country coverage area Siima sells') and immediately scopes it with concrete examples ('Europe+', 'South East Asia', 'CENAM') plus worldwide plans. It also names what each result contains, so an agent can distinguish it from list_destinations at a glance.

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?

Explicit when-to-use ('Use this for a trip crossing several countries'), explicit routing to the alternative ('For a single-country trip use list_destinations instead'), and a follow-up workflow with search_esim_plans and get_esim_plan. This is a complete decision path.

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

search_esim_plansSearch Siima travel eSIM plansAInspect

Search prepaid travel eSIM data plans by destination country (ISO 3166-1 alpha-2, e.g. "JP"), region (e.g. "Europe"), minimum data in GB, maximum total price, or plan duration in days. Plans come in three coverage types: "country" (one country), "regional" (a named multi-country area such as "Europe+" or "South East Asia"), and "global" (worldwide). A country filter matches every plan that covers it, of any coverage type — so searching country="FR" returns France-only plans alongside the Europe and worldwide plans that include France. For a trip through several countries, filter coverage_type="regional" or "global" to get one eSIM for the whole route; for a single-country trip a "country" plan is usually cheapest. Returned price is the final amount the customer pays at checkout (all fees included), in the requested currency. To buy: call create_checkout_link with the plan id, give the returned URL to the user. They confirm their email with a 6-digit code and pay there; nothing is ordered until they do. After payment they are emailed a link to their eSIM; opening it on their phone gives a one-tap install, the QR code and manual codes. No account needed.

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoMax results to return
regionNoRegion name, e.g. "Europe", "Asia"
countryNoDestination country as ISO 3166-1 alpha-2 code, e.g. "JP" for Japan. Matches plans of any coverage type that include it.
coverageNoExact coverage area name for a regional or worldwide plan, e.g. "Europe+", "CENAM", "Global" — get valid names from list_regions
currencyNoCurrency for prices: "usd", "eur", or "gbp". Defaults to "usd".usd
max_priceNoMaximum total price in the requested currency (checkout total)
min_data_gbNoMinimum data allowance in GB
coverage_typeNoRestrict to single-country plans, multi-country regional plans, or worldwide plans
duration_daysNoExact plan duration in days

TDQS

A4.6/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden and does so well: it explains the semantics of the country filter (matches any coverage type that includes it, with a concrete FR example), states that price is the final checkout total with all fees, and describes the downstream purchase flow, email verification, and eSIM delivery. This is far beyond what the schema provides.

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

Conciseness4/5

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

Filter semantics are front-loaded and structured logically, then the purchase flow is appended. The purchase-flow portion (email code, link, one-tap install, QR) is useful but somewhat beyond what a search tool needs, making it slightly longer than strictly required.

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?

For a 9-parameter, 0-required filter tool with no output schema, the description covers filter semantics, coverage-type behavior, price meaning, and the hand-off to purchasing. Nothing an agent needs to select and invoke this correctly is missing; only the result shape is unstated, which is a minor gap for a search tool.

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 genuine meaning for the country/coverage_type/coverage filters (cross-type matching, the three coverage categories), but duplicates the currency and price semantics already documented in the schema, so it does not exceed the baseline.

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?

Specific verb+resource ("search prepaid travel eSIM data plans") with the full set of filter dimensions enumerated. It also clearly distinguishes itself from siblings by naming the purchase path (create_checkout_link) and the region-name lookup (implied via schema reference to list_regions).

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 tells the agent which filter to choose for a multi-country trip (coverage_type="regional"/"global") versus a single-country trip ("country" plan is cheapest), and routes purchasing to create_checkout_link with the plan id. Both when-to-use guidance and the alternative tool are named.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedcreate_checkout_link1 field changed
      • changedInput schema / properties / email / description
        Previous value: -"Buyer email to pre-fill at checkout (eSIM is delivered to this address)"New value: +"Buyer email to pre-fill at checkout (they verify it before paying; the eSIM is delivered there)"
  2. 2 tool updates
    • Addedlist_regions
    • Changedsearch_esim_plans3 fields changed
      • changedInput schema / properties / country / description
        Previous value: -"Destination country as ISO 3166-1 alpha-2 code, e.g. \"JP\" for Japan"New value: +"Destination country as ISO 3166-1 alpha-2 code, e.g. \"JP\" for Japan. Matches plans of any coverage type that include it."
      • addedInput schema / properties / coverage
        Added value: +{
+  "description": "Exact coverage area name for a regional or worldwide plan, e.g. \"Europe+\", \"CENAM\", \"Global\" — get valid names from list_regions",
+  "type": "string"
+}
      • addedInput schema / properties / coverage_type
        Added value: +{
+  "description": "Restrict to single-country plans, multi-country regional plans, or worldwide plans",
+  "enum": [
+    "country",
+    "regional",
+    "global"
+  ],
+  "type": "string"
+}
  3. 4 tool updates
    • Changedcreate_checkout_link1 field changed
      • addedInput schema / properties / currency
        Added value: +{
+  "default": "usd",
+  "description": "Currency for prices: \"usd\", \"eur\", or \"gbp\". Defaults to \"usd\".",
+  "enum": [
+    "usd",
+    "eur",
+    "gbp"
+  ],
+  "type": "string"
+}
    • Changedget_esim_plan1 field changed
      • addedInput schema / properties / currency
        Added value: +{
+  "default": "usd",
+  "description": "Currency for prices: \"usd\", \"eur\", or \"gbp\". Defaults to \"usd\".",
+  "enum": [
+    "usd",
+    "eur",
+    "gbp"
+  ],
+  "type": "string"
+}
    • Changedlist_destinations2 fields changed
      • addedInput schema / additionalProperties
        Added value: +false
      • addedInput schema / properties / currency
        Added value: +{
+  "default": "usd",
+  "description": "Currency for prices: \"usd\", \"eur\", or \"gbp\". Defaults to \"usd\".",
+  "enum": [
+    "usd",
+    "eur",
+    "gbp"
+  ],
+  "type": "string"
+}
    • Changedsearch_esim_plans3 fields changed
      • addedInput schema / properties / currency
        Added value: +{
+  "default": "usd",
+  "description": "Currency for prices: \"usd\", \"eur\", or \"gbp\". Defaults to \"usd\".",
+  "enum": [
+    "usd",
+    "eur",
+    "gbp"
+  ],
+  "type": "string"
+}
      • addedInput schema / properties / max_price
        Added value: +{
+  "description": "Maximum total price in the requested currency (checkout total)",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}
      • removedInput schema / properties / max_price_usd
        Removed value: -{
-  "description": "Maximum total price in USD (checkout total)",
-  "exclusiveMinimum": 0,
-  "type": "number"
-}
  4. 4 tool updates
    • First observedcreate_checkout_link
    • First observedget_esim_plan
    • First observedlist_destinations
    • First observedsearch_esim_plans

Related MCP Connectors

Related MCP Servers

  • esim-mcp-server

    Stoneip
    -
    license
    Not graded
    quality
    B
    maintenance
    Lets AI agents search and buy travel eSIMs from ALT eSIM for 200+ destinations, with Stripe payment links and email delivery of QR codes.
    -

  • SinoConnection eSIM

    SkyUnlimit
    A
    license
    Not graded
    quality
    D
    maintenance
    Search and buy travel eSIMs for 200+ countries, with specialized China plans that deliver uncensored internet without a VPN. Exposes five read-only tools to search plans, check device eSIM compatibility, get plan details, get help, and generate a secure on-site checkout link.
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources