Siima eSIM

Search Siima travel eSIM plans

search_esim_plans

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 the eSIM (QR code + activation link + manual codes) is emailed to them automatically — no account needed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max results to return
`region`	No	Region name, e.g. "Europe", "Asia"
`country`	No	Destination country as ISO 3166-1 alpha-2 code, e.g. "JP" for Japan. Matches plans of any coverage type that include it.
`coverage`	No	Exact coverage area name for a regional or worldwide plan, e.g. "Europe+", "CENAM", "Global" — get valid names from list_regions
`currency`	No	Currency for prices: "usd", "eur", or "gbp". Defaults to "usd".	usd
`max_price`	No	Maximum total price in the requested currency (checkout total)
`min_data_gb`	No	Minimum data allowance in GB
`coverage_type`	No	Restrict to single-country plans, multi-country regional plans, or worldwide plans
`duration_days`	No	Exact plan duration in days

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedAug 11, 2026

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"
+}

Changed3 schema fields changedJul 24, 2026

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"
-}

First observedJul 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations, the description carries the full burden, and it explains key non-obvious behavior: a country filter matches plans of any coverage type that include that country, prices are final all-in checkout totals, and nothing is ordered until the user confirms and pays. It also states that the eSIM is emailed automatically with no account needed.

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?

The description is longer than average but front-loaded with the search purpose and filters, and each section adds value: coverage semantics, price semantics, and the follow-up purchase flow. The purchase-flow sentences could arguably live in create_checkout_link, but they support the end-to-end task without feeling padded.

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 tool with 9 optional parameters, no annotations, and no output schema, the description is remarkably complete: it explains the coverage model, filter interactions, price behavior, and the required next step for purchase. The exact result object shape is not specified, but the plan id and price semantics are already stated, so an agent can invoke and follow up correctly.

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 the baseline is 3, but the description adds meaningful semantics beyond the schema: country matches any coverage type, price is the final checkout amount in the requested currency, and coverage_type maps to single-country, regional, or worldwide plans. This clarifies the two most ambiguous parameters.

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 opens with a specific verb and resource: 'Search prepaid travel eSIM data plans' and enumerates the filter dimensions. It distinguishes itself from the purchase sibling by explicitly saying 'To buy: call create_checkout_link', and the coverage-type explanation makes its scope clear.

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?

It gives concrete selection guidance: for multi-country trips filter coverage_type='regional' or 'global', while for single-country trips a 'country' plan is usually cheapest. It also names create_checkout_link as the buy-path alternative, though it does not explicitly tell the agent when to prefer list_regions or get_esim_plan.

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

All Siima eSIM tools Inspect

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

Need Help?