Skip to main content
Glama

Search eSIM plans

search_plans
Read-onlyIdempotent

Find available travel data eSIM plans for a country, city, region, or ISO-2 destination such as 'Japan', 'Tokyo', 'Europe', or 'TR'. Filter by minimum validity (days), minimum data (data_gb), unlimited-only, maximum EUR budget and sort order; returns matching plans, price/validity details and a cheapest-match recommendation, without reserving stock. Use get_plan to validate a selected plan before prepare_order and list_destinations if a location is not recognized.

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

Input Schema

NameRequiredDescriptionDefault
daysNoMinimum validity in days (trip length).
langNoLanguage for names and texts (default en).
sortNo
limitNo
data_gbNoMinimum data in GB.
unlimitedNoOnly unlimited (true) or only fixed-data (false) plans.
destinationYesCountry, city, region or ISO-2 code.
max_price_eurNoMaximum price in EUR.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "en",
      -  "de",
      -  "ru",
      -  "uk",
      -  "pl",
      -  "nl",
      -  "it",
      -  "es",
      -  "fr",
      -  "tr"
      -]New value: +[
      +  "en",
      +  "de",
      +  "ru",
      +  "uk",
      +  "pl",
      +  "nl",
      +  "it",
      +  "es",
      +  "fr",
      +  "tr",
      +  "pt",
      +  "ro",
      +  "cs",
      +  "sv",
      +  "sk"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "en",
      -  "de",
      -  "ru",
      -  "uk",
      -  "pl",
      -  "nl",
      -  "it",
      -  "es",
      -  "fr",
      -  "tr",
      -  "pt",
      -  "ro",
      -  "cs",
      -  "sv",
      -  "sk"
      -]New value: +[
      +  "en",
      +  "de",
      +  "ru",
      +  "uk",
      +  "pl",
      +  "nl",
      +  "it",
      +  "es",
      +  "fr",
      +  "tr"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "en",
      -  "de",
      -  "ru",
      -  "uk",
      -  "pl",
      -  "nl",
      -  "it",
      -  "es",
      -  "fr",
      -  "tr"
      -]New value: +[
      +  "en",
      +  "de",
      +  "ru",
      +  "uk",
      +  "pl",
      +  "nl",
      +  "it",
      +  "es",
      +  "fr",
      +  "tr",
      +  "pt",
      +  "ro",
      +  "cs",
      +  "sv",
      +  "sk"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "en",
      -  "de",
      -  "ru",
      -  "uk",
      -  "pl",
      -  "nl",
      -  "it",
      -  "es",
      -  "fr",
      -  "tr",
      -  "pt",
      -  "ro",
      -  "cs",
      -  "sv",
      -  "sk"
      -]New value: +[
      +  "en",
      +  "de",
      +  "ru",
      +  "uk",
      +  "pl",
      +  "nl",
      +  "it",
      +  "es",
      +  "fr",
      +  "tr"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "en",
      -  "de",
      -  "ru",
      -  "uk",
      -  "pl",
      -  "nl",
      -  "it",
      -  "es",
      -  "fr",
      -  "tr"
      -]New value: +[
      +  "en",
      +  "de",
      +  "ru",
      +  "uk",
      +  "pl",
      +  "nl",
      +  "it",
      +  "es",
      +  "fr",
      +  "tr",
      +  "pt",
      +  "ro",
      +  "cs",
      +  "sv",
      +  "sk"
      +]
  6. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "en",
      -  "de",
      -  "ru",
      -  "uk",
      -  "pl",
      -  "nl"
      -]New value: +[
      +  "en",
      +  "de",
      +  "ru",
      +  "uk",
      +  "pl",
      +  "nl",
      +  "it",
      +  "es",
      +  "fr",
      +  "tr"
      +]
  7. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "en",
      -  "de",
      -  "ru",
      -  "uk"
      -]New value: +[
      +  "en",
      +  "de",
      +  "ru",
      +  "uk",
      +  "pl",
      +  "nl"
      +]
  8. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, and the description meaningfully adds that it does not reserve stock and that results include a cheapest-match recommendation. It stops short of describing result count limits or pagination behavior, but the key side-effect profile is 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?

Two front-loaded sentences: capability and filters first, downstream tool routing last. Dense but nearly every clause carries information; the long destination-example list is slightly verbose but aids disambiguation.

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 8 parameters and no output schema, the description usefully explains the return payload (matching plans, price/validity, cheapest-match recommendation) and the downstream workflow. Gaps remain around default limit behavior and the compare_plans alternative, so it is strong but not exhaustive.

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 75%, so most parameters are already documented in the schema. The description reinforces the filter semantics (min validity as trip length, min data, unlimited-only, max EUR budget, sort order) but adds no new detail for 'limit' or 'lang', which are undocumented in both places.

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 ('Find available travel data eSIM plans') plus the accepted destination forms with concrete examples ('Japan', 'Tokyo', 'Europe', 'TR'). It is clearly distinguishable from get_plan (validating one plan) and list_destinations (resolving unknown locations).

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: use get_plan to validate before prepare_order, and list_destinations when a location is not recognized. It does not address when to use this versus the sibling compare_plans, which is the closest overlapping tool, so the alternative-routing is incomplete.

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