Skip to main content
Glama

Find eSIM plans for a destination

search_plans
Read-only

Use this when someone needs mobile data for a trip to ONE country or wants a regional pass (Europe, Asia, Balkans, Global…). Returns the GlobalPass travel eSIM plans on sale there: data, validity, final price, networks and a link to buy each plan. Data only: no calls or SMS. For a route through several countries call plan_trip instead.

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
daysNoLength of the stay in days, if known.
data_gbNoGigabytes needed for the whole stay, if known.
currencyNoCurrency for prices. Defaults to PLN for Polish and EUR otherwise; use USD for dollar cards.
languageNoThe traveller's language for names and for the pages the links open: en, pl or ru.
destinationYesA country or region as the traveller says it, in English, Polish or Russian, or an ISO code: "Turkey", "Egipt", "ОАЭ", "Europe", "TR".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and catalog scope are covered. The description usefully adds that results are data-only with no calls or SMS and lists the returned fields, but says nothing about result volume, pagination, or what happens when no plans match the destination.

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?

Three compact sentences, each earning its place: the trigger first, then the return payload, then the constraint and the sibling routing. The "Data only: no calls or SMS" line is a high-value clarification delivered in six words.

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?

Five parameters, all documented in-schema, no output schema, and the description compensates by enumerating the returned fields. For a read-only lookup tool with a sibling handoff spelled out, nothing an agent needs in order to call it correctly 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 every parameter already carries its own description, including the enum values and destination examples. The description adds no syntax, format, or defaulting information beyond what the schema supplies, so the baseline of 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?

Names a specific verb and resource (returns GlobalPass travel eSIM plans) and states the exact scope: one country or a regional pass. It also enumerates what each plan carries (data, validity, final price, networks, buy link), so the agent knows precisely what comes back without opening anything else.

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?

Opens with the triggering condition ("Use this when someone needs mobile data for a trip to ONE country or wants a regional pass") and names the explicit alternative for the excluded case: multi-country routes should call plan_trip instead. Both the when and the when-not are stated outright.

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