Skip to main content
Glama

Find travel eSIM plans

find_esim_plans
Read-onlyIdempotent

Prepaid data-only travel eSIM plans from SimOwl for a country or region, cheapest first, with prices and a buy_url. Includes regional plans that also cover the country. Give the person the buy_url of the plan they choose: the plan opens already selected, they enter their email and pay; the QR code arrives by email within minutes.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax plans to return (default 30, max 100).
currencyNoISO 4217 code to quote prices in (USD, EUR, GBP, JPY...). Defaults to EUR when not sold.
min_daysNoOnly plans valid for at least this many days (trip length).
destinationYesCountry name or ISO 3166-1 alpha-2 code ("Japan", "JP"), or a region ("Europe", "Asia Pacific").
min_data_gbNoOnly plans with at least this much data (unlimited plans always match).
unlimited_onlyNoOnly unlimited-data plans.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish that this is a safe read-only, idempotent, closed-world lookup, so the description doesn't need to restate safety. It adds real behavioral context the annotations lack: results are sorted cheapest-first and regional plans covering the country are included, plus what the returned buy_url does when opened. It doesn't mention result volume/pagination behavior beyond the limit parameter.

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 what the tool returns and how results are ordered, then the destination scope, then the checkout-flow instruction. Every sentence carries information, though the QR-code/email detail is slightly more than an agent strictly needs to select and invoke the tool.

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?

There is no output schema, so the description correctly covers return content (plans, prices, buy_url) and ordering. For a read-only search tool with fully documented parameters this is close to complete; only result-volume or empty-result behavior is left unstated.

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 all six parameters including currency defaults, min_days, and unlimited_only are already fully documented in the schema. The description adds only marginal semantic value by clarifying that region lookups also surface regional plans that cover the destination. Baseline 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?

The description names a specific resource (prepaid data-only travel eSIM plans from SimOwl), the lookup key (country or region), and the ordering (cheapest first). It effectively states what comes back (prices, buy_url) but never contrasts itself with siblings like list_esim_destinations or estimate_trip_data, so it stops short of a 5.

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?

It gives downstream workflow guidance ('give the person the buy_url of the plan they choose' and what happens after payment), which is genuinely useful. However, there is no guidance on when to call this versus the sibling tools (e.g., check support first, estimate data first), so the routing decision is left implicit.

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