Skip to main content
Glama

eSIMCompare: travel eSIM prices

Search travel eSIM plans

search_esim_plans
Read-onlyIdempotent

Find the cheapest travel eSIM data plans for a destination from 34 providers (Airalo, Holafly, Nomad eSIM, Saily, Ubigi, Yesim and more), filtered to what a trip needs. Returns plans sorted by price (cheapest first) with data allowance, validity, price, price per GB, local network, speed policy, the date the price was checked, a page on eSIMCompare that cites the source, and a buy link. A buy link is an eSIMCompare address that takes a person on to the provider's own page for that plan after they press Continue; give it to the person rather than fetching it, since a program that opens it is shown that Continue page and not the provider. Buy links marked affiliate_link may earn eSIMCompare a commission; the price is the provider's own either way. For a provider eSIMCompare has no partnership with, the buy link is the plan's page on eSIMCompare, which offers comparable plans that can be bought through it, and where a buy link applies a reader discount the plan also gives price_through_buy_url_usd.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "destination": "<destination>"
    },
    "name": "search_esim_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many plans to return (default 5).
trip_daysNoTrip length in days: plans must stay valid at least this long.
destinationYesCountry or region, by name or ISO code: 'Japan', 'JP', 'United States', 'Europe', 'Global'.
min_data_gbNoLeast data the trip needs, in GB. Unlimited plans always qualify.
max_price_usdNoHighest total price in US dollars.
unlimited_onlyNoOnly unlimited-data plans.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare a safe, read-only, idempotent, closed-world search, and the description adds substantial behavior beyond them: results are sorted cheapest-first, the exact return fields (price per GB, network, speed policy, price-check date, citation page, buy link), the affiliate_link flag and its meaning, and the price_through_buy_url_usd caveat. It also discloses the non-obvious trap that programmatic fetches of buy links hit a Continue interstitial rather than the provider.

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 purpose and return shape are front-loaded, and the buy-link paragraph, while dense, earns its space because no output schema exists to carry that information. Some of the affiliate-link and reader-discount exposition is verbose and could be tightened, but nothing is redundant with structured fields.

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, the description carries the full burden of explaining return values and does so thoroughly, including sort order, per-plan fields, and the meaning of the buy link and its variants. For a 6-parameter, fully documented read-only search, an agent has everything needed to call it and interpret results correctly.

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 every parameter (destination, trip_days, min_data_gb, max_price_usd, unlimited_only, limit) is already documented, and the description adds little per-parameter meaning beyond the phrase "filtered to what a trip needs." The 34-provider scope and cheapest-first ordering are useful framing but not parameter semantics, 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?

"Find the cheapest travel eSIM data plans for a destination from 34 providers" states a specific verb (find/search), resource (travel eSIM data plans), scope (a destination), and even names the source set. It is instantly distinguishable from compare_esim_providers and esim_price_index, which by name imply comparison/index views rather than a filtered plan search.

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 clear contextual guidance on how to use the output: buy links should be handed to the person, not fetched, because a program that opens them sees a Continue page. It also frames the search as "filtered to what a trip needs." It stops short of explicitly naming when to prefer compare_esim_providers or esim_price_index, so there is no exclusion guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources