Skip to main content
Glama

Find travel eSIM plans

find_esim_plans
Read-only

Lists Inbox eSIM data plans for a destination (country, city, region such as Europe, or 'global'), cheapest first, with plan_id, data in GB, validity in days and price in USD. Data only, no phone number; works on unlocked eSIM phones.

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
min_daysNoOptional: only plans valid for at least this many days (the trip length).
destinationYesWhere the customer travels, e.g. 'Japan', 'USA', 'Europe', 'Bangkok'.
min_data_gbNoOptional: only plans with at least this much data.

Output Schema

NameRequiredDescriptionDefault
noteNo
plansYes

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?

The annotations already establish that this is a read-only, non-destructive, non-open-world operation. The description adds useful behavioral context beyond annotations: results are cheapest first, contain specific fields, cover data-only plans with no phone number, and require an unlocked eSIM phone. Pagination and rate limits are not covered, but the annotation baseline lowers that burden.

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?

The description is two tight sentences, front-loaded with purpose and then key result and device details. There is no filler, and the return-field list is brief enough to aid selection even though an output schema exists.

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?

For a simple read-only lookup with full schema coverage, annotations, and an output schema, this description covers the essential context: destination scope, ordering, data-only limitation, and unlocked-device requirement. Missing pagination or result caps are minor for this tool's complexity.

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 description coverage is 100%, so the schema already explains all three parameters and the baseline would be 3. The description adds destination semantics beyond the schema examples, clarifying that destination can be a country, city, region such as Europe, or 'global'; it adds less for min_days and min_data_gb.

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 states a specific verb and resource: it lists eSIM data plans for a destination, with ordering and returned fields. It is clear on its own, but it does not explicitly differentiate itself from siblings such as compare_esim_prices or buy_esim.

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: this is the tool for finding available plans for a destination, and it notes data-only and unlocked-phone constraints. However, it never says when to use this instead of compare_esim_prices, buy_esim, or make_esim_cart, nor does it state any exclusions.

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