eSIM-Global.VIP eSIM Catalog

Server Details

Find prepaid travel eSIM plans for 200+ destinations with live prices, specs and a buy link.

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 21 days
Last Tested: 2026-10-03 09:47
Transport: Streamable HTTP · MCP 2025-06-18
URL

TDQS

A4.3/5.0

Scored 2026-09-29 16:05 across 5 tools

Disambiguation5/5

Each tool has a clearly distinct role: get_plan_details fetches one plan by product id, get_shop_facts answers general shop questions, recommend_plan handles trip-based recommendations, search_esim_plans handles destination-based plan discovery, and start_checkout handles purchase handoff. The overlapping discovery tools are explicitly differentiated by trip description versus destination query. No two tools appear to do the same thing.

Naming Consistency5/5

All tool names use consistent snake_case with a predictable verb_noun or verb_noun_phrase pattern: get_plan_details, get_shop_facts, recommend_plan, search_esim_plans, start_checkout. The convention is uniform throughout. No mixed casing or vague verb styles.

Tool Count5/5

Five tools are well-scoped for an eSIM catalog and purchase flow. Each tool earns its place across discovery, recommendation, detail lookup, shop facts, and checkout. There is no redundant or filler tool.

Completeness4/5

The surface covers the main customer journey: search, recommend, inspect a plan, understand shop policies, and start checkout. Minor gaps remain for post-purchase actions such as order tracking, top-up execution, or refund handling, though some of these are explicitly out of scope or only described. Overall the core lifecycle is well covered.

Available Tools

5 tools

get_plan_detailsGet plan detailsA

Read-onlyIdempotent

Inspect

Full facts for one eSIM-Global.VIP plan by product id: coverage with networks per country, data and speed rules, activation and validity rules, hotspot / APN / registration facts, top-up, refund rule, price with basis, reviews and link — quoted in the customer's bucket or currency when given.

ParametersJSON Schema

Name	Required	Description
`bucket`	No	Optional language-region bucket the customer shops in, e.g. "en-gb", "de-de". Wins over language; prices and links are quoted in it.
`currency`	No	Optional ISO 4217 code. Every price in the result is quoted in it.
`language`	No	ISO language of the conversation, e.g. en, de, ja. Plan names and country names come back in it when available. Bare "en" is quoted in en-us / USD.
`product_id`	Yes	Product id from search_esim_plans or recommend_plan.

Output Schema

ParametersJSON Schema

Name	Required	Description
`apn`	No	APN to set when the vendor requires one.
`sku`	No	Catalogue SKU.
`url`	No	Product page in pricing_bucket. Use verbatim.
`data`	No	Data Pack: total data label, e.g. "5GB".
`days`	No	Validity in days (Data Pack, Daily Pack).
`name`	No	Short plan name: destination · data · validity · type.
`type`	No	Plan type.
`price`	No	Price in currency, read WITH price_basis: the full price of the plan when "total", the price of ONE day when "per_day". Never a per-GB rate. The price shown is the price paid.
`title`	No	Full product title in the requested language.
`topup`	No	Top-up possibility for this plan.
`rating`	No	Average customer rating (1-5). Present only when reviews exist.
`data_gb`	No	Data amount in GB. Meaning given by data_period.
`hotspot`	No	Hotspot / tethering rule as the vendor states it, e.g. "Supported" or a device limit.
`summary`	No	Short description in the requested language, from the product page.
`currency`	No	ISO 4217 currency of every price in this object.
`fair_use`	No	Fair-use policy text from the supplier, when stated.
`networks`	No	Operator names across the plan (deduplicated). Per-country detail is in coverage_countries.
`validity`	No	Validity label, e.g. "30 days".
`plan_note`	No	One-sentence vendor fact to present verbatim when present; overrides the generic type description.
`price_max`	No	Only on price_basis "per_day": the price for the longest duration in days_range, discount applied — the figure to quote for a full period. Never infer it by multiplying.
`speed_cap`	No	Present only on plans with a PERMANENT speed cap, e.g. "10 Mbit/s". Never call such a plan high-speed.
`voice_sms`	No	Always "none": data only, no telephone number, no SMS.
`covers_via`	No	Present when the plan was returned for a country it covers as part of a multi-country plan: the plan's own region name.
`days_range`	No	Unlimited Flex: choosable durations in days, e.g. "1-30".
`expires_on`	No	Stock expiry date (YYYY-MM-DD) when the product itself has one.
`product_id`	No	Product id. Use it for get_plan_details and start_checkout.
`data_period`	No	"total": data_gb is the whole plan (Data Pack). "per_day": data_gb is the daily full-speed allowance (Unlimited Flex, Daily Pack).
`ip_breakout`	No	Country whose internet connection the customer appears to use (IP breakout), ISO code(s) — matters for banking apps, streaming and mainland-China access. Vendor fact.
`price_basis`	No	What `price` means.
`refund_rule`	No	The refund class in words - present verbatim.
`kyc_required`	No	true when the vendor requires real-name registration (ID verification) on arrival before data works.
`last_updated`	No	Date the plan was last updated in the catalogue (YYYY-MM-DD).
`refund_class`	No	Vendor refund/cancellation class for this plan.
`review_count`	No	Number of reviews. Present only when > 0.
`transparency`	No	A per-order Transparency link shows remaining data in near real-time.
`coverage_note`	No	Coverage caveat to present verbatim, e.g. traffic routed via Hong Kong.
`always_on_rate`	No	Unlimited Flex / Daily Pack: reduced speed after the daily allowance, e.g. "512 Kbit/s". Empty when the plan has a speed_cap or is unlimited.
`coverage_count`	No	Number of countries in coverage_countries.
`price_is_final`	No	Always true: no tax or fee is added at checkout.
`pricing_bucket`	No	language-region bucket the prices and links are quoted in, e.g. "en-us".
`daily_high_speed`	No	Unlimited Flex / Daily Pack: daily allowance at full speed, e.g. "2GB"; "unlimited" = unlimited data every day at full speed (fair-use policy).
`daily_reset_time`	No	When the daily allowance resets, as the vendor states it (clock and time zone). Absent = resets 24 h after activation is NOT implied; simply unknown.
`unused_valid_days`	No	Days the eSIM may remain unused after purchase before it expires (supplier value).
`activation_trigger`	No	"install": validity and billing start the moment the eSIM is installed — install only when ready to use. "first_connection": the eSIM can be installed before travel; validity starts on first connection to a network at the destination.
`coverage_countries`	No	Every country the plan works in, with the network operators per country when known.
`network_generation`	No	Network technology, e.g. "4G/LTE/5G". Never an operator name.
`start_date_required`	No	true when a start date must be chosen at checkout.
`install_before_travel`	No	true when the eSIM can safely be installed before departure (activation_trigger first_connection).

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered. The description adds real behavioral context beyond them: prices and links are quoted per the customer's bucket or currency, and it enumerates the fact categories returned, which helps the agent know what it is asking for.

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?

A single dense sentence that front-loads the verb and the identifying key (product id) before the long facet enumeration. The list is heavy but each item names a distinct returned facet, so little is wasted.

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?

With annotations covering the safety profile and an output schema presumably documenting the return shape, the description is complete enough: it names the lookup key, the override semantics for pricing, and the scope of facts. Nothing critical for a correct invocation is missing.

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 bucket, currency, language and product_id are fully documented in the schema. The description only restates the quoting behavior ('quoted in the customer's bucket or currency when given') without adding syntax or precedence detail beyond what the schema already gives.

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+resource ('Full facts for one eSIM-Global.VIP plan by product id') and enumerates the exact facets returned (coverage, data rules, hotspot/APN, top-up, refund, price basis, reviews). This clearly separates it from search_esim_plans and recommend_plan, which supply the id this tool consumes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The singular 'one plan by product id' framing implies this is the detail-lookup step after a search or recommendation, but there is no explicit when-to-use/when-not statement or named alternative. Usage is only inferred from the phrase 'by product id'.

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

get_shop_factsShop factsA

Read-onlyIdempotent

Inspect

How eSIM-Global.VIP works, in the shop's own words: delivery and installation, device requirements, payment methods, money-back guarantee, top-up, hotspot, support and company details. Use for any "how / when / what if" question that is not about one specific plan.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds non-obvious value by enumerating the topical coverage of the returned facts and flagging that content is unstructured prose ('in the shop's own words'), which helps the agent anticipate the response shape. It does not discuss output format or freshness, but the output schema exists.

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, no filler: the first defines the content, the second defines the routing rule. The usage rule is front-loaded second, right where an agent deciding between siblings will look.

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 zero parameters, an output schema present, and annotations covering the safety profile, the only remaining burden is scope and routing — both delivered precisely. Nothing needed to call this correctly is missing.

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?

The tool takes zero parameters, so the baseline is 4. There is nothing for the description to disambiguate; its content list is a faithful preview of the result rather than parameter guidance.

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 the resource (shop-level facts about how eSIM-Global.VIP works) and enumerates the exact content domains it covers: delivery/installation, device requirements, payment, guarantee, top-up, hotspot, support, company details. The closing clause explicitly demarcates it from plan-specific siblings, so an agent can route without opening a schema.

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?

Gives a clear usage trigger ('any how / when / what if question') plus an explicit exclusion ('not about one specific plan'). It stops short of naming get_plan_details or search_esim_plans as the alternative for the excluded case, leaving that inference to the agent.

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

recommend_planRecommend a plan for a tripA

Read-onlyIdempotent

Inspect

Turn a trip into up to three plan recommendations: countries (1-5, any language), number of days and how much data the traveller uses. Each fit carries the full plan facts, the total price for the whole trip and a one-sentence reason built only from catalogue facts. Use this first whenever the user describes a trip rather than asks for a list.

ParametersJSON Schema

Name	Required	Description
`days`	Yes	Trip length in days.
`usage`	No	light ≈ 0.5 GB/day (maps, messaging), normal ≈ 1.5 GB/day (social, some video), heavy ≈ 4 GB/day (video, hotspot). Default normal.
`bucket`	No	Optional language-region bucket the customer shops in, e.g. "en-gb", "de-de". Wins over language; prices and links are quoted in it.
`budget`	No	Optional maximum total for the trip, in the result currency.
`currency`	No	Optional ISO 4217 code. Every price in the result is quoted in it.
`language`	No	ISO language of the conversation, e.g. en, de, ja. Plan names and country names come back in it when available. Bare "en" is quoted in en-us / USD.
`countries`	Yes	Countries or regions of the trip, any language.
`gb_per_day`	No	Overrides usage with an explicit daily need in GB.

Output Schema

ParametersJSON Schema

Name	Required	Description
`trip`	No
`message`	No
`currency`	No
`all_plans_url`	No
`pricing_bucket`	No
`recommendations`	No

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds useful behavioral detail: up to three recommendations, each carrying full plan facts, total price, and a one-sentence reason built only from catalogue facts. No contradiction with annotations.

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?

Three sentences, front-loaded with purpose and inputs, then output details, then usage. The middle sentence describing return content is somewhat redundant given an output schema exists, but overall the description is efficient and well-structured.

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 annotations covering safety, a comprehensive schema, and an output schema, the description needs only to state purpose, usage context, and high-level output shape. It does all three adequately; no critical information for correct invocation is missing.

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 the schema already documents all eight parameters with detail. The description restates the key inputs (countries 1-5, days, usage) but adds no syntax or meaning beyond what the schema provides, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (recommend) and resource (plan for a trip), and specifies the output (up to three recommendations). The phrase 'rather than asks for a list' implicitly distinguishes it from sibling search_esim_plans, though no sibling is named explicitly.

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?

Provides clear when-to-use guidance: 'Use this first whenever the user describes a trip rather than asks for a list.' This sets context and implies an exclusion (list requests), but does not explicitly name alternatives like search_esim_plans or get_plan_details.

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

search_esim_plansFind eSIM plansA

Read-onlyIdempotent

Inspect

Find eSIM-Global.VIP eSIM plans for one destination or several (countries or regions, any language). Returns the best-value plans first with full facts, coverage lists and a direct link; multi-country plans that include the destination are returned too and marked covers_via. Use when a user wants mobile data abroad; use recommend_plan when they describe a whole trip.

ParametersJSON Schema

Name	Required	Description
`sort`	No	value = best price per GB / cheapest Flex first (default); price = cheapest first; data = most data first.
`type`	No	Plan type. Default any.
`limit`	No	Plans to return. Default 10; all_plans_url lists everything.
`bucket`	No	Optional language-region bucket the customer shops in, e.g. "en-gb", "de-de". Wins over language; prices and links are quoted in it.
`currency`	No	Optional ISO 4217 code. Every price in the result is quoted in it.
`language`	No	ISO language of the conversation, e.g. en, de, ja. Plan names and country names come back in it when available. Bare "en" is quoted in en-us / USD.
`min_days`	No	Only plans valid for at least this many days (Unlimited Flex counts when days_range allows it).
`destination`	No	Country or region in any language, e.g. "Thailand", "Japon", "Europa", or a 2-letter ISO code. For a city, pass its country.
`destinations`	No	Several countries for one trip; only plans covering ALL of them are returned. Overrides destination.

Output Schema

ParametersJSON Schema

Name	Required	Description
`iso`	No	Resolved ISO code or region slug of the (first) destination.
`note`	No	Present when part of the request could not be honoured (e.g. more than 5 destinations).
`plans`	No
`covered`	No
`message`	No	Present when nothing matched: says why and what to try.
`currency`	No
`returned`	No
`from_price`	No	Lowest price in this result set, shop-formatted (per-day plans count with their day price).
`destination`	No
`destinations`	No	How each requested destination was understood.
`all_plans_url`	No
`pricing_bucket`	No
`total_available`	No	Plans matched before limit; the rest are on all_plans_url.

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description goes beyond them by disclosing result ordering ("best-value plans first"), the inclusion of multi-country plans flagged as covers_via, and the return payload shape (facts, coverage lists, direct link). It stops short of detailing pagination or result limits.

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, zero filler, and the structure is front-loaded: what is returned first, then when to reach for it and which sibling to prefer instead. Every clause carries routing or result information.

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 9 optional parameters at full schema coverage, complete annotations, and an output schema that documents return values, the description needs only to supply scope and routing — which it does. Nothing an agent needs before invoking this tool is missing.

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% and the enum semantics for sort/type are fully documented in the schema, so the baseline is 3. The description contributes only the loose hints that destinations may be any language and that several destinations constitute one trip — helpful framing, but nothing the schema does not already establish.

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+resource ("Find eSIM plans") and immediately bounds the scope to one or several destinations, in any language. It also explicitly distinguishes itself from the sibling recommend_plan, so an agent can route correctly without opening either schema.

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?

Gives an explicit trigger ("Use when a user wants mobile data abroad") plus the disambiguation rule for the alternative ("use recommend_plan when they describe a whole trip"). This is exactly the when/when-not/alternative split the dimension asks for.

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

start_checkoutStart secure checkoutA

Read-onlyIdempotent

Inspect

Hand the customer to the eSIM-Global.VIP shop to buy one plan. Returns buy_url (the product page where they tap Buy now and pay securely — card, Apple Pay, Google Pay, PayPal, with an optional discount code) plus the plan name and price in the customer's bucket or currency. No account needed; the eSIM is emailed right after payment. There is no in-chat order tracking.

ParametersJSON Schema

Name	Required	Description
`days`	No	Unlimited Flex only: the duration the customer wants; the returned total_for_days is the checkout total for it.
`bucket`	No	Optional language-region bucket the customer shops in, e.g. "en-gb", "de-de". Wins over language; prices and links are quoted in it.
`currency`	No	Optional ISO 4217 code. Every price in the result is quoted in it.
`language`	No	ISO language of the conversation, e.g. en, de, ja. Plan names and country names come back in it when available. Bare "en" is quoted in en-us / USD.
`product_id`	Yes	Product id to buy.

Output Schema

ParametersJSON Schema

Name	Required	Description
`days`	No
`price`	No	Read WITH price_basis.
`buy_url`	No	The exact product page to send the customer to. Use verbatim.
`message`	No
`product`	No
`currency`	No
`price_max`	No
`days_range`	No
`product_id`	No
`price_basis`	No
`presentation`	No
`price_is_final`	No
`pricing_bucket`	No
`total_for_days`	No	Unlimited Flex: checkout total for the requested days, discount applied.

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent, and the description adds substantial context beyond them: it returns a buy_url, the accepted payment methods, that no account is needed, that the eSIM is emailed after payment, and that no in-chat tracking exists. This tells the agent exactly what the side-effect boundary is (a link handoff, not an in-chat order).

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 the action and outcome, then supporting details; the payment-methods aside and delivery note are relevant rather than filler. Slightly dense with parentheticals, but every sentence carries information.

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 output schema covers the return shape and annotations cover the safety profile, the description fills the remaining gaps an agent needs: external handoff behavior, payment options, account requirement, post-payment delivery, and the absence of in-chat tracking.

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% and an output schema exists, so the baseline is 3. The description only loosely reinforces bucket/currency ('in the customer's bucket or currency') and adds no format or precedence detail beyond what the schema already states; the 'Unlimited Flex only' semantics for days live in the schema, not here.

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 ('Hand the customer to the ... shop to buy one plan'), with an explicit scope limit ('one plan') and a named destination. It is clearly distinguishable from siblings like search_esim_plans, get_plan_details and recommend_plan, which do not hand off to checkout.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied ('buy one plan') and a negative constraint is given ('There is no in-chat order tracking'), but there is no explicit when-to-use versus the sibling tools or a stated prerequisite (e.g. 'call after recommend_plan / with a product_id from search_esim_plans'). The agent must infer where this fits in the flow.

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.

3 tool updatesSep 29, 2026

Changedget_plan_details2 fields changed

addedOutput schema / properties / last_updated

Added value: +{
+  "description": "Date the plan was last updated in the catalogue (YYYY-MM-DD).",
+  "type": "string"
+}

removedOutput schema / properties / last_verified

Removed value: -{
-  "description": "Date the plan facts were last synchronised from the supplier (YYYY-MM-DD), when known.",
-  "type": "string"
-}

Changedrecommend_plan2 fields changed

addedOutput schema / properties / recommendations / items / properties / plan / properties / last_updated

Added value: +{
+  "description": "Date the plan was last updated in the catalogue (YYYY-MM-DD).",
+  "type": "string"
+}

removedOutput schema / properties / recommendations / items / properties / plan / properties / last_verified

Removed value: -{
-  "description": "Date the plan facts were last synchronised from the supplier (YYYY-MM-DD), when known.",
-  "type": "string"
-}

Changedsearch_esim_plans4 fields changed

changedOutput schema / properties / from_price / description

Previous value: -"Localized \"from\" price string."New value: +"Lowest price in this result set, shop-formatted (per-day plans count with their day price)."

addedOutput schema / properties / note

Added value: +{
+  "description": "Present when part of the request could not be honoured (e.g. more than 5 destinations).",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / last_updated

Added value: +{
+  "description": "Date the plan was last updated in the catalogue (YYYY-MM-DD).",
+  "type": "string"
+}

removedOutput schema / properties / plans / items / properties / last_verified

Removed value: -{
-  "description": "Date the plan facts were last synchronised from the supplier (YYYY-MM-DD), when known.",
-  "type": "string"
-}

5 tool updatesSep 29, 2026

Changedget_plan_details60 fields changed

addedInput schema / properties / bucket

Added value: +{
+  "description": "Optional language-region bucket the customer shops in, e.g. \"en-gb\", \"de-de\". Wins over language; prices and links are quoted in it.",
+  "type": "string"
+}

addedInput schema / properties / currency

Added value: +{
+  "description": "Optional ISO 4217 code. Every price in the result is quoted in it.",
+  "type": "string"
+}

changedInput schema / properties / language / description

Previous value: -"ISO language of the conversation. Sets the landing-page language/currency of the link."New value: +"ISO language of the conversation, e.g. en, de, ja. Plan names and country names come back in it when available. Bare \"en\" is quoted in en-us / USD."

changedInput schema / properties / product_id / description

Previous value: -"WooCommerce product id from search_esim_plans."New value: +"Product id from search_esim_plans or recommend_plan."

addedOutput schema / description

Added value: +"One eSIM plan. Every field is present only when the catalogue holds a value for it; an absent field is unknown, never \"no\"."

addedOutput schema / properties / activation_trigger

Added value: +{
+  "description": "\"install\": validity and billing start the moment the eSIM is installed — install only when ready to use. \"first_connection\": the eSIM can be installed before travel; validity starts on first connection to a network at the destination.",
+  "enum": [
+    "install",
+    "first_connection"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / always_on_rate / description

Previous value: -"Unlimited Flex / Daily Pack: reduced rate after the daily allowance. Empty when the plan has a speed_cap (no reduction moment) or is unlimited."New value: +"Unlimited Flex / Daily Pack: reduced speed after the daily allowance, e.g. \"512 Kbit/s\". Empty when the plan has a speed_cap or is unlimited."

addedOutput schema / properties / apn

Added value: +{
+  "description": "APN to set when the vendor requires one.",
+  "type": "string"
+}

addedOutput schema / properties / coverage_count

Added value: +{
+  "description": "Number of countries in coverage_countries.",
+  "type": "integer"
+}

addedOutput schema / properties / coverage_countries

Added value: +{
+  "description": "Every country the plan works in, with the network operators per country when known.",
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "iso": {
+        "description": "ISO 3166-1 alpha-2, lowercase.",
+        "type": "string"
+      },
+      "name": {
+        "description": "Country name in the requested language.",
+        "type": "string"
+      },
+      "networks": {
+        "description": "Operator names in that country, as the supplier lists them.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / coverage_note

Added value: +{
+  "description": "Coverage caveat to present verbatim, e.g. traffic routed via Hong Kong.",
+  "type": "string"
+}

addedOutput schema / properties / covers_via

Added value: +{
+  "description": "Present when the plan was returned for a country it covers as part of a multi-country plan: the plan's own region name.",
+  "type": "string"
+}

addedOutput schema / properties / currency / description

Added value: +"ISO 4217 currency of every price in this object."

addedOutput schema / properties / daily_reset_time

Added value: +{
+  "description": "When the daily allowance resets, as the vendor states it (clock and time zone). Absent = resets 24 h after activation is NOT implied; simply unknown.",
+  "type": "string"
+}

changedOutput schema / properties / data / description

Previous value: -"Data Pack: total data label."New value: +"Data Pack: total data label, e.g. \"5GB\"."

addedOutput schema / properties / data_gb / description

Added value: +"Data amount in GB. Meaning given by data_period."

addedOutput schema / properties / data_period

Added value: +{
+  "description": "\"total\": data_gb is the whole plan (Data Pack). \"per_day\": data_gb is the daily full-speed allowance (Unlimited Flex, Daily Pack).",
+  "enum": [
+    "total",
+    "per_day"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / days

Added value: +{
+  "description": "Validity in days (Data Pack, Daily Pack).",
+  "type": "integer"
+}

changedOutput schema / properties / days_range / description

Previous value: -"Only on price_basis \"per_day\": the durations the customer can choose, in days, e.g. \"1-30\"."New value: +"Unlimited Flex: choosable durations in days, e.g. \"1-30\"."

removedOutput schema / properties / description
```
Removed value: -{
-  "type": "string"
-}
```

addedOutput schema / properties / expires_on

Added value: +{
+  "description": "Stock expiry date (YYYY-MM-DD) when the product itself has one.",
+  "type": "string"
+}

addedOutput schema / properties / fair_use

Added value: +{
+  "description": "Fair-use policy text from the supplier, when stated.",
+  "type": "string"
+}

addedOutput schema / properties / hotspot

Added value: +{
+  "description": "Hotspot / tethering rule as the vendor states it, e.g. \"Supported\" or a device limit.",
+  "type": "string"
+}

addedOutput schema / properties / install_before_travel

Added value: +{
+  "description": "true when the eSIM can safely be installed before departure (activation_trigger first_connection).",
+  "type": "boolean"
+}

addedOutput schema / properties / ip_breakout

Added value: +{
+  "description": "Country whose internet connection the customer appears to use (IP breakout), ISO code(s) — matters for banking apps, streaming and mainland-China access. Vendor fact.",
+  "type": "string"
+}

addedOutput schema / properties / kyc_required

Added value: +{
+  "description": "true when the vendor requires real-name registration (ID verification) on arrival before data works.",
+  "type": "boolean"
+}

addedOutput schema / properties / last_verified

Added value: +{
+  "description": "Date the plan facts were last synchronised from the supplier (YYYY-MM-DD), when known.",
+  "type": "string"
+}

addedOutput schema / properties / name / description

Added value: +"Short plan name: destination · data · validity · type."

removedOutput schema / properties / network

Removed value: -{
-  "description": "Speed token only (e.g. 4G/LTE/5G) — never a carrier/operator name.",
-  "type": "string"
-}

addedOutput schema / properties / network_generation

Added value: +{
+  "description": "Network technology, e.g. \"4G/LTE/5G\". Never an operator name.",
+  "type": "string"
+}

addedOutput schema / properties / networks

Added value: +{
+  "description": "Operator names across the plan (deduplicated). Per-country detail is in coverage_countries.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / plan_note / description

Previous value: -"One-sentence vendor fact to present verbatim (in the user's language) when present; overrides the generic Unlimited Flex description."New value: +"One-sentence vendor fact to present verbatim when present; overrides the generic type description."

changedOutput schema / properties / price / description

Previous value: -"Price in currency, to be read WITH price_basis: the full fixed price of the plan when price_basis is \"total\", the price of one day when it is \"per_day\". Never a per-GB rate."New value: +"Price in currency, read WITH price_basis: the full price of the plan when \"total\", the price of ONE day when \"per_day\". Never a per-GB rate. The price shown is the price paid."

changedOutput schema / properties / price_basis / description

Previous value: -"What `price` means. \"total\" = the whole plan (Data Pack, Daily Pack). \"per_day\" = one day (Unlimited Flex): the duration is chosen at checkout within days_range and price_max is the longest-duration price."New value: +"What `price` means."

addedOutput schema / properties / price_is_final

Added value: +{
+  "description": "Always true: no tax or fee is added at checkout.",
+  "type": "boolean"
+}

changedOutput schema / properties / price_max / description

Previous value: -"Only on price_basis \"per_day\": the price for the longest duration in days_range, discount already applied — the figure to quote for a full period. Absent when it cannot be computed; never infer it by multiplying price."New value: +"Only on price_basis \"per_day\": the price for the longest duration in days_range, discount applied — the figure to quote for a full period. Never infer it by multiplying."

addedOutput schema / properties / pricing_bucket

Added value: +{
+  "description": "language-region bucket the prices and links are quoted in, e.g. \"en-us\".",
+  "type": "string"
+}

addedOutput schema / properties / product_id / description

Added value: +"Product id. Use it for get_plan_details and start_checkout."

addedOutput schema / properties / rating / description

Added value: +"Average customer rating (1-5). Present only when reviews exist."

addedOutput schema / properties / refund_class

Added value: +{
+  "description": "Vendor refund/cancellation class for this plan.",
+  "enum": [
+    "until_install",
+    "non_refundable",
+    "no_cancel"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / refund_rule

Added value: +{
+  "description": "The refund class in words - present verbatim.",
+  "type": "string"
+}

addedOutput schema / properties / review_count / description

Added value: +"Number of reviews. Present only when > 0."

addedOutput schema / properties / sku

Added value: +{
+  "description": "Catalogue SKU.",
+  "type": "string"
+}

changedOutput schema / properties / speed_cap / description

Previous value: -"Present only on plans with a PERMANENT speed cap, e.g. \"10 Mbit/s\": the plan always runs at up to this speed with the daily allowance in daily_high_speed. Do not call such a plan high-speed."New value: +"Present only on plans with a PERMANENT speed cap, e.g. \"10 Mbit/s\". Never call such a plan high-speed."

addedOutput schema / properties / start_date_required

Added value: +{
+  "description": "true when a start date must be chosen at checkout.",
+  "type": "boolean"
+}

addedOutput schema / properties / summary

Added value: +{
+  "description": "Short description in the requested language, from the product page.",
+  "type": "string"
+}

removedOutput schema / properties / tethering
```
Removed value: -{
-  "type": "boolean"
-}
```

addedOutput schema / properties / title

Added value: +{
+  "description": "Full product title in the requested language.",
+  "type": "string"
+}

addedOutput schema / properties / topup / additionalProperties
```
Added value: +true
```

changedOutput schema / properties / topup / description

Previous value: -"True only for data top-up (add data to a Data Pack). See topup_kind for the full picture."New value: +"Top-up possibility for this plan."

addedOutput schema / properties / topup / properties

Added value: +{
+  "how": {
+    "description": "How the customer tops up.",
+    "type": "string"
+  },
+  "kind": {
+    "description": "What TopUp can add without a new eSIM: data (Data Pack), days (Unlimited Flex / Daily Pack), or none.",
+    "enum": [
+      "data",
+      "days",
+      "none"
+    ],
+    "type": "string"
+  }
+}

changedOutput schema / properties / topup / type

Previous value: -"boolean"New value: +"object"

removedOutput schema / properties / topup_kind

Removed value: -{
-  "description": "What eSIM-Global.VIP TopUp can add to this plan without a new eSIM: \"data\" (Data Pack), \"days\" (Unlimited Flex / Daily Pack: extend validity), or \"none\".",
-  "enum": [
-    "data",
-    "days",
-    "none"
-  ],
-  "type": "string"
-}

addedOutput schema / properties / transparency / description

Added value: +"A per-order Transparency link shows remaining data in near real-time."

changedOutput schema / properties / type / description

Previous value: -"Data Pack, Daily Pack or Unlimited Flex."New value: +"Plan type."

addedOutput schema / properties / type / enum

Added value: +[
+  "Data Pack",
+  "Daily Pack",
+  "Unlimited Flex"
+]

addedOutput schema / properties / unused_valid_days

Added value: +{
+  "description": "Days the eSIM may remain unused after purchase before it expires (supplier value).",
+  "type": "integer"
+}

addedOutput schema / properties / url / description

Added value: +"Product page in pricing_bucket. Use verbatim."

changedOutput schema / properties / validity / description

Previous value: -"Data Pack: validity label."New value: +"Validity label, e.g. \"30 days\"."

addedOutput schema / properties / voice_sms

Added value: +{
+  "description": "Always \"none\": data only, no telephone number, no SMS.",
+  "type": "string"
+}

Addedget_shop_facts
Addedrecommend_plan

Changedsearch_esim_plans71 fields changed

addedInput schema / properties / bucket

Added value: +{
+  "description": "Optional language-region bucket the customer shops in, e.g. \"en-gb\", \"de-de\". Wins over language; prices and links are quoted in it.",
+  "type": "string"
+}

changedInput schema / properties / currency / description

Previous value: -"Optional ISO 4217 override for the headline \"from\" price. Normally derived from language."New value: +"Optional ISO 4217 code. Every price in the result is quoted in it."

changedInput schema / properties / destination / description

Previous value: -"Country or region in English, e.g. \"Thailand\", \"Japan\", \"Europe\", or a 2-letter ISO code. If the user names a city (e.g. \"Tokyo\"), pass its country (\"Japan\")."New value: +"Country or region in any language, e.g. \"Thailand\", \"Japon\", \"Europa\", or a 2-letter ISO code. For a city, pass its country."

addedInput schema / properties / destinations

Added value: +{
+  "description": "Several countries for one trip; only plans covering ALL of them are returned. Overrides destination.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 5,
+  "type": "array"
+}

changedInput schema / properties / language / description

Previous value: -"ISO language of the conversation, e.g. en, de, ja, th. Sets the landing-page language and currency."New value: +"ISO language of the conversation, e.g. en, de, ja. Plan names and country names come back in it when available. Bare \"en\" is quoted in en-us / USD."

addedInput schema / properties / limit

Added value: +{
+  "description": "Plans to return. Default 10; all_plans_url lists everything.",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / min_days

Added value: +{
+  "description": "Only plans valid for at least this many days (Unlimited Flex counts when days_range allows it).",
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / sort

Added value: +{
+  "description": "value = best price per GB / cheapest Flex first (default); price = cheapest first; data = most data first.",
+  "enum": [
+    "value",
+    "price",
+    "data"
+  ],
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "destination"
-]New value: +[]

addedOutput schema / properties / destinations

Added value: +{
+  "description": "How each requested destination was understood.",
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "iso": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "query": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / iso / description

Added value: +"Resolved ISO code or region slug of the (first) destination."

addedOutput schema / properties / message / description

Added value: +"Present when nothing matched: says why and what to try."

addedOutput schema / properties / plans / items / description

Added value: +"One eSIM plan. Every field is present only when the catalogue holds a value for it; an absent field is unknown, never \"no\"."

addedOutput schema / properties / plans / items / properties / activation_trigger

Added value: +{
+  "description": "\"install\": validity and billing start the moment the eSIM is installed — install only when ready to use. \"first_connection\": the eSIM can be installed before travel; validity starts on first connection to a network at the destination.",
+  "enum": [
+    "install",
+    "first_connection"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / plans / items / properties / always_on_rate / description

Previous value: -"Unlimited Flex / Daily Pack: reduced rate after the daily allowance. Empty when the plan has a speed_cap (no reduction moment) or is unlimited."New value: +"Unlimited Flex / Daily Pack: reduced speed after the daily allowance, e.g. \"512 Kbit/s\". Empty when the plan has a speed_cap or is unlimited."

addedOutput schema / properties / plans / items / properties / apn

Added value: +{
+  "description": "APN to set when the vendor requires one.",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / coverage_count

Added value: +{
+  "description": "Number of countries in coverage_countries.",
+  "type": "integer"
+}

addedOutput schema / properties / plans / items / properties / coverage_countries

Added value: +{
+  "description": "Every country the plan works in, with the network operators per country when known.",
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "iso": {
+        "description": "ISO 3166-1 alpha-2, lowercase.",
+        "type": "string"
+      },
+      "name": {
+        "description": "Country name in the requested language.",
+        "type": "string"
+      },
+      "networks": {
+        "description": "Operator names in that country, as the supplier lists them.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / plans / items / properties / coverage_note

Added value: +{
+  "description": "Coverage caveat to present verbatim, e.g. traffic routed via Hong Kong.",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / covers_via

Added value: +{
+  "description": "Present when the plan was returned for a country it covers as part of a multi-country plan: the plan's own region name.",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / currency / description
```
Added value: +"ISO 4217 currency of every price in this object."
```

addedOutput schema / properties / plans / items / properties / daily_reset_time

Added value: +{
+  "description": "When the daily allowance resets, as the vendor states it (clock and time zone). Absent = resets 24 h after activation is NOT implied; simply unknown.",
+  "type": "string"
+}

changedOutput schema / properties / plans / items / properties / data / description

Previous value: -"Data Pack: total data label."New value: +"Data Pack: total data label, e.g. \"5GB\"."

addedOutput schema / properties / plans / items / properties / data_gb / description
```
Added value: +"Data amount in GB. Meaning given by data_period."
```

addedOutput schema / properties / plans / items / properties / data_period

Added value: +{
+  "description": "\"total\": data_gb is the whole plan (Data Pack). \"per_day\": data_gb is the daily full-speed allowance (Unlimited Flex, Daily Pack).",
+  "enum": [
+    "total",
+    "per_day"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / days

Added value: +{
+  "description": "Validity in days (Data Pack, Daily Pack).",
+  "type": "integer"
+}

changedOutput schema / properties / plans / items / properties / days_range / description

Previous value: -"Only on price_basis \"per_day\": the durations the customer can choose, in days, e.g. \"1-30\"."New value: +"Unlimited Flex: choosable durations in days, e.g. \"1-30\"."

removedOutput schema / properties / plans / items / properties / description
```
Removed value: -{
-  "type": "string"
-}
```

addedOutput schema / properties / plans / items / properties / expires_on

Added value: +{
+  "description": "Stock expiry date (YYYY-MM-DD) when the product itself has one.",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / fair_use

Added value: +{
+  "description": "Fair-use policy text from the supplier, when stated.",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / hotspot

Added value: +{
+  "description": "Hotspot / tethering rule as the vendor states it, e.g. \"Supported\" or a device limit.",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / install_before_travel

Added value: +{
+  "description": "true when the eSIM can safely be installed before departure (activation_trigger first_connection).",
+  "type": "boolean"
+}

addedOutput schema / properties / plans / items / properties / ip_breakout

Added value: +{
+  "description": "Country whose internet connection the customer appears to use (IP breakout), ISO code(s) — matters for banking apps, streaming and mainland-China access. Vendor fact.",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / kyc_required

Added value: +{
+  "description": "true when the vendor requires real-name registration (ID verification) on arrival before data works.",
+  "type": "boolean"
+}

addedOutput schema / properties / plans / items / properties / last_verified

Added value: +{
+  "description": "Date the plan facts were last synchronised from the supplier (YYYY-MM-DD), when known.",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / name / description
```
Added value: +"Short plan name: destination · data · validity · type."
```

removedOutput schema / properties / plans / items / properties / network

Removed value: -{
-  "description": "Speed token only (e.g. 4G/LTE/5G) — never a carrier/operator name.",
-  "type": "string"
-}

addedOutput schema / properties / plans / items / properties / network_generation

Added value: +{
+  "description": "Network technology, e.g. \"4G/LTE/5G\". Never an operator name.",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / networks

Added value: +{
+  "description": "Operator names across the plan (deduplicated). Per-country detail is in coverage_countries.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / plans / items / properties / plan_note / description

Previous value: -"One-sentence vendor fact to present verbatim (in the user's language) when present; overrides the generic Unlimited Flex description."New value: +"One-sentence vendor fact to present verbatim when present; overrides the generic type description."

changedOutput schema / properties / plans / items / properties / price / description

Previous value: -"Price in currency, to be read WITH price_basis: the full fixed price of the plan when price_basis is \"total\", the price of one day when it is \"per_day\". Never a per-GB rate."New value: +"Price in currency, read WITH price_basis: the full price of the plan when \"total\", the price of ONE day when \"per_day\". Never a per-GB rate. The price shown is the price paid."

changedOutput schema / properties / plans / items / properties / price_basis / description

Previous value: -"What `price` means. \"total\" = the whole plan (Data Pack, Daily Pack). \"per_day\" = one day (Unlimited Flex): the duration is chosen at checkout within days_range and price_max is the longest-duration price."New value: +"What `price` means."

addedOutput schema / properties / plans / items / properties / price_is_final

Added value: +{
+  "description": "Always true: no tax or fee is added at checkout.",
+  "type": "boolean"
+}

changedOutput schema / properties / plans / items / properties / price_max / description

Previous value: -"Only on price_basis \"per_day\": the price for the longest duration in days_range, discount already applied — the figure to quote for a full period. Absent when it cannot be computed; never infer it by multiplying price."New value: +"Only on price_basis \"per_day\": the price for the longest duration in days_range, discount applied — the figure to quote for a full period. Never infer it by multiplying."

addedOutput schema / properties / plans / items / properties / pricing_bucket

Added value: +{
+  "description": "language-region bucket the prices and links are quoted in, e.g. \"en-us\".",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / product_id / description
```
Added value: +"Product id. Use it for get_plan_details and start_checkout."
```
addedOutput schema / properties / plans / items / properties / rating / description
```
Added value: +"Average customer rating (1-5). Present only when reviews exist."
```

addedOutput schema / properties / plans / items / properties / refund_class

Added value: +{
+  "description": "Vendor refund/cancellation class for this plan.",
+  "enum": [
+    "until_install",
+    "non_refundable",
+    "no_cancel"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / refund_rule

Added value: +{
+  "description": "The refund class in words - present verbatim.",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / review_count / description
```
Added value: +"Number of reviews. Present only when > 0."
```

addedOutput schema / properties / plans / items / properties / sku

Added value: +{
+  "description": "Catalogue SKU.",
+  "type": "string"
+}

changedOutput schema / properties / plans / items / properties / speed_cap / description

Previous value: -"Present only on plans with a PERMANENT speed cap, e.g. \"10 Mbit/s\": the plan always runs at up to this speed with the daily allowance in daily_high_speed. Do not call such a plan high-speed."New value: +"Present only on plans with a PERMANENT speed cap, e.g. \"10 Mbit/s\". Never call such a plan high-speed."

addedOutput schema / properties / plans / items / properties / start_date_required

Added value: +{
+  "description": "true when a start date must be chosen at checkout.",
+  "type": "boolean"
+}

addedOutput schema / properties / plans / items / properties / summary

Added value: +{
+  "description": "Short description in the requested language, from the product page.",
+  "type": "string"
+}

removedOutput schema / properties / plans / items / properties / tethering
```
Removed value: -{
-  "type": "boolean"
-}
```

addedOutput schema / properties / plans / items / properties / title

Added value: +{
+  "description": "Full product title in the requested language.",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / topup / additionalProperties
```
Added value: +true
```

changedOutput schema / properties / plans / items / properties / topup / description

Previous value: -"True only for data top-up (add data to a Data Pack). See topup_kind for the full picture."New value: +"Top-up possibility for this plan."

addedOutput schema / properties / plans / items / properties / topup / properties

Added value: +{
+  "how": {
+    "description": "How the customer tops up.",
+    "type": "string"
+  },
+  "kind": {
+    "description": "What TopUp can add without a new eSIM: data (Data Pack), days (Unlimited Flex / Daily Pack), or none.",
+    "enum": [
+      "data",
+      "days",
+      "none"
+    ],
+    "type": "string"
+  }
+}

changedOutput schema / properties / plans / items / properties / topup / type
```
Previous value: -"boolean"New value: +"object"
```

removedOutput schema / properties / plans / items / properties / topup_kind

Removed value: -{
-  "description": "What eSIM-Global.VIP TopUp can add to this plan without a new eSIM: \"data\" (Data Pack), \"days\" (Unlimited Flex / Daily Pack: extend validity), or \"none\".",
-  "enum": [
-    "data",
-    "days",
-    "none"
-  ],
-  "type": "string"
-}

addedOutput schema / properties / plans / items / properties / transparency / description
```
Added value: +"A per-order Transparency link shows remaining data in near real-time."
```

changedOutput schema / properties / plans / items / properties / type / description

Previous value: -"Data Pack, Daily Pack or Unlimited Flex."New value: +"Plan type."

addedOutput schema / properties / plans / items / properties / type / enum

Added value: +[
+  "Data Pack",
+  "Daily Pack",
+  "Unlimited Flex"
+]

addedOutput schema / properties / plans / items / properties / unused_valid_days

Added value: +{
+  "description": "Days the eSIM may remain unused after purchase before it expires (supplier value).",
+  "type": "integer"
+}

addedOutput schema / properties / plans / items / properties / url / description
```
Added value: +"Product page in pricing_bucket. Use verbatim."
```

changedOutput schema / properties / plans / items / properties / validity / description

Previous value: -"Data Pack: validity label."New value: +"Validity label, e.g. \"30 days\"."

addedOutput schema / properties / plans / items / properties / voice_sms

Added value: +{
+  "description": "Always \"none\": data only, no telephone number, no SMS.",
+  "type": "string"
+}

addedOutput schema / properties / pricing_bucket
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / returned
```
Added value: +{
+  "type": "integer"
+}
```

addedOutput schema / properties / total_available

Added value: +{
+  "description": "Plans matched before limit; the rest are on all_plans_url.",
+  "type": "integer"
+}

Changedstart_checkout15 fields changed

addedInput schema / properties / bucket

Added value: +{
+  "description": "Optional language-region bucket the customer shops in, e.g. \"en-gb\", \"de-de\". Wins over language; prices and links are quoted in it.",
+  "type": "string"
+}

addedInput schema / properties / currency

Added value: +{
+  "description": "Optional ISO 4217 code. Every price in the result is quoted in it.",
+  "type": "string"
+}

addedInput schema / properties / days

Added value: +{
+  "description": "Unlimited Flex only: the duration the customer wants; the returned total_for_days is the checkout total for it.",
+  "minimum": 1,
+  "type": "integer"
+}

changedInput schema / properties / language / description

Previous value: -"ISO language of the conversation. Sets the language/currency of the payment page."New value: +"ISO language of the conversation, e.g. en, de, ja. Plan names and country names come back in it when available. Bare \"en\" is quoted in en-us / USD."

changedInput schema / properties / product_id / description

Previous value: -"WooCommerce product id to buy."New value: +"Product id to buy."

addedOutput schema / properties / days
```
Added value: +{
+  "type": "integer"
+}
```

removedOutput schema / properties / days_range / description

Removed value: -"Only on price_basis \"per_day\": choosable durations in days, e.g. \"1-30\"."

addedOutput schema / properties / presentation
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / price / description

Previous value: -"Price in currency, to be read WITH price_basis: the full fixed price when \"total\", the price of one day when \"per_day\"."New value: +"Read WITH price_basis."

removedOutput schema / properties / price_basis / description

Removed value: -"What `price` means for this product. See the plan schema."

addedOutput schema / properties / price_is_final
```
Added value: +{
+  "type": "boolean"
+}
```

removedOutput schema / properties / price_max / description

Removed value: -"Only on price_basis \"per_day\": price for the longest duration, discount applied."

addedOutput schema / properties / pricing_bucket
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / product_id
```
Added value: +{
+  "type": "integer"
+}
```

addedOutput schema / properties / total_for_days

Added value: +{
+  "description": "Unlimited Flex: checkout total for the requested days, discount applied.",
+  "type": "number"
+}

3 tool updatesSep 22, 2026

Changedget_plan_details4 fields changed

addedOutput schema / properties / days_range

Added value: +{
+  "description": "Only on price_basis \"per_day\": the durations the customer can choose, in days, e.g. \"1-30\".",
+  "type": "string"
+}

changedOutput schema / properties / price / description

Previous value: -"Full fixed price in currency; not per-day or per-GB."New value: +"Price in currency, to be read WITH price_basis: the full fixed price of the plan when price_basis is \"total\", the price of one day when it is \"per_day\". Never a per-GB rate."

addedOutput schema / properties / price_basis

Added value: +{
+  "description": "What `price` means. \"total\" = the whole plan (Data Pack, Daily Pack). \"per_day\" = one day (Unlimited Flex): the duration is chosen at checkout within days_range and price_max is the longest-duration price.",
+  "enum": [
+    "total",
+    "per_day"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / price_max

Added value: +{
+  "description": "Only on price_basis \"per_day\": the price for the longest duration in days_range, discount already applied — the figure to quote for a full period. Absent when it cannot be computed; never infer it by multiplying price.",
+  "type": "number"
+}

Changedsearch_esim_plans4 fields changed

addedOutput schema / properties / plans / items / properties / days_range

Added value: +{
+  "description": "Only on price_basis \"per_day\": the durations the customer can choose, in days, e.g. \"1-30\".",
+  "type": "string"
+}

changedOutput schema / properties / plans / items / properties / price / description

Previous value: -"Full fixed price in currency; not per-day or per-GB."New value: +"Price in currency, to be read WITH price_basis: the full fixed price of the plan when price_basis is \"total\", the price of one day when it is \"per_day\". Never a per-GB rate."

addedOutput schema / properties / plans / items / properties / price_basis

Added value: +{
+  "description": "What `price` means. \"total\" = the whole plan (Data Pack, Daily Pack). \"per_day\" = one day (Unlimited Flex): the duration is chosen at checkout within days_range and price_max is the longest-duration price.",
+  "enum": [
+    "total",
+    "per_day"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / price_max

Added value: +{
+  "description": "Only on price_basis \"per_day\": the price for the longest duration in days_range, discount already applied — the figure to quote for a full period. Absent when it cannot be computed; never infer it by multiplying price.",
+  "type": "number"
+}

Changedstart_checkout4 fields changed

addedOutput schema / properties / days_range

Added value: +{
+  "description": "Only on price_basis \"per_day\": choosable durations in days, e.g. \"1-30\".",
+  "type": "string"
+}

changedOutput schema / properties / price / description

Previous value: -"Full fixed price in currency; not per-day."New value: +"Price in currency, to be read WITH price_basis: the full fixed price when \"total\", the price of one day when \"per_day\"."

addedOutput schema / properties / price_basis

Added value: +{
+  "description": "What `price` means for this product. See the plan schema.",
+  "enum": [
+    "total",
+    "per_day"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / price_max

Added value: +{
+  "description": "Only on price_basis \"per_day\": price for the longest duration, discount applied.",
+  "type": "number"
+}

3 tool updatesSep 13, 2026
- First observedget_plan_details
- First observedsearch_esim_plans
- First observedstart_checkout

Related MCP Connectors

IbiPoint eSIM Catalog A
com.ibipoint
Search prepaid travel eSIM data plans for 200+ countries with live prices and a buy link.
Travel & Transportation E-commerce & Retail
51
Roam2Go eSIM Catalog A
com.roam2go
Search travel eSIM data plans for 230+ destinations with live prices and purchase links.
Travel & Transportation E-commerce & Retail Search
31
e-eSIM Catalog A
com.e-esim
Search travel eSIM data plans worldwide with live prices, plan details and a buy link.
Travel & Transportation E-commerce & Retail
51
eSIM Finder AOAuth
io.esimfinder
Search, compare & buy prepaid travel eSIM data plans for 190+ countries in 40 currencies, including regional plans and a 12-month Travel Pass.
E-commerce & Retail Search Travel & Transportation
52

Related MCP Servers

esimoaofficial
E-commerce & Retail
nbase-io
A
license
Not graded
quality
C
maintenance
Enables AI assistants to search and compare travel eSIM data plans by destination, trip length, data amount, unlimited/daily type, local phone number, local or roaming network, multi-country coverage, budget, hotspot and 5G, returning plan details plus a link to buy. Read-only with no sign-in or API key required.
Updated a day ago (2026-10-02 10:59 UTC)
1
MIT
PikaSim
Travel & Transportation E-commerce & Retail Cryptocurrency
codebruinc
A
license
Not graded
quality
D
maintenance
Browse, compare, and purchase eSIMs for 190+ countries via AI agents. 12 tools for searching 2,300+ data plans, checking coverage, and buying eSIMs with crypto or card. No account required for browsing.
Updated 2 months ago (2026-07-28 03:00 UTC)
MIT
SinoConnection eSIM
Travel & Transportation E-commerce & Retail
SkyUnlimit
A
license
Not graded
quality
C
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.
Updated 3 months ago (2026-07-16 16:52 UTC)
MIT
mcp-esim
Travel & Transportation E-commerce & Retail Payments & Billing
isabellaliebgott
A
license
A
quality
D
maintenance
Travel eSIMs for 193 countries. Stripe + Bitcoin checkout. QR by email in 30s. No API key.
Updated 4 months ago (2026-06-07 12:48 UTC)
4
58 npm
MIT