Skip to main content
Glama

OsmO Travel eSIM

Search eSIM plans

search_esim_plans
Read-onlyIdempotent

Use this when the user is travelling abroad and wants mobile data, an eSIM, a travel SIM, or to avoid roaming charges. Finds eSIM plans in the OsmO catalogue that cover the whole trip, including multi-country trips, and ranks them by the published rule: fit first, then total price. Trip length is required. Covers data plans from the providers listed in the result. Does not handle home-country phone contracts or purchases.

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": {
      "trip": "<trip>"
    },
    "name": "search_esim_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
tripYes
limitNo
needsNo
usageNoPhone use if dataGb is unknown: light (~0.3 GB/day), moderate (~0.8), heavy (~2)
dataGbNoData needed per person in GB; omit to estimate from usage
unlimitedNotrue = only unlimited-data plans
travellersNoPeople travelling; each needs their own eSIM
maxPriceUsdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive search over a closed catalogue (openWorldHint=false). The description adds behavior the annotations cannot convey: results are ranked by a published rule (fit first, then total price), coverage is judged against the whole multi-leg trip, and the provider set is that of the returned results. It does not describe result count behavior or what happens when no plan covers the trip.

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?

Four sentences, front-loaded with the trigger scenario before the mechanics and the exclusion at the end — a sensible order. Minor padding in the near-synonym list ('an eSIM, a travel SIM'), but nothing is wasted enough to obscure the call.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nested 8-parameter search with no output schema, the description covers the purpose, ranking, and trip-length requirement but leaves the filter parameters (needs, unlimited, maxPriceUsd, travellers, limit) and the zero-coverage case unexplained. Adequate to call correctly on the required path, thin for an agent trying to use the optional filters well.

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 50% across 8 parameters, so the description must carry some weight, and it does add one real constraint: 'Trip length is required,' which is not obvious from the schema where only 'trip' is required and totalDays/legs.days are optional. Beyond that it says nothing about needs, unlimited, maxPriceUsd, travellers, or limit, leaving half the surface to the schema alone — the 3 baseline is warranted.

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?

States a specific verb and resource ('Finds eSIM plans in the OsmO catalogue') plus the scope it handles ('plans that cover the whole trip, including multi-country trips'). The ranking rule (fit first, then total price) further pins down what the tool actually returns, though it never names a sibling like compare_esim_plans or show_esim_plans to separate itself from the adjacent tools in the catalog.

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?

The opening sentence gives a concrete trigger set ('travelling abroad', 'mobile data', 'an eSIM', 'a travel SIM', 'avoid roaming charges'), and the closing sentence gives an explicit exclusion ('Does not handle home-country phone contracts or purchases'). What's missing is routing: no alternative tool is named for the compare/show/get cases an agent will encounter next to this one.

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