Skip to main content
Glama

Find eSIM data plans

search_plans
Read-only

Prepaid travel eSIM data plans from Tutu eSIM (tutuesim.com) for a country or a region, with today's prices in USD and a link to buy. Fixed-data plans (GB for N days) and unlimited day passes. The eSIM is data-only, installs by QR or one tap, and its validity starts at the first connection abroad.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
gbNoAt least this much data (fixed plans)
srcNoAttribution tag for the buy links (default mcp)
daysNoAt least this many days
langNoLanguage of the names and the link; uk adds ≈ UAH
limitNoMax plans (default 8)
regionNoInstead of a country: a regional or the global plan
countryNoISO 3166 code (EG, TR) or the name in English, Ukrainian or Russian
unlimitedNoOnly unlimited day passes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious product behavior: data-only, QR or one-tap install, and validity starting at first connection abroad, plus that prices are USD and include a buy link. It stops short of describing sorting, ranking, or what happens when no plans match.

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 tight sentences: what it returns first, then plan taxonomy, then product mechanics. Nothing repeats the schema or annotations, and no sentence is filler.

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 8 fully documented optional parameters, no output schema, and annotations covering safety, the description supplies exactly the missing layer: what a result contains (USD price, buy link) and what the product is (data-only, activation at first use). An agent can call and explain results without further context.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds interpretable meaning: it explains the two plan families (fixed-data GB for N days vs unlimited day passes), which is what makes the gb/days/unlimited filters intelligible as a set. It still does not clarify the relationship between country and region when both or neither are supplied.

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?

Specific verb+resource: finds prepaid travel eSIM data plans from a named provider for a country or region, and states what comes back (today's prices in USD, buy link). It does not explicitly distinguish itself from sibling compare_prices or get_country, so an agent must infer the boundary rather than being told.

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 by the parameter set (country or region) and by the framing as a plan lookup, but there is no explicit when-to-use/when-not text and no named alternative such as compare_prices or roaming_cost. An agent can guess the context but is not routed.

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