Skip to main content
Glama

Find eSIM plans

plans_find
Read-only

List the SimOptions travel eSIM plans in stock for a trip. With one destination code: the plans its page on simoptions.com lists. With several: the plans that cover every one of them. Destination codes come from destinations_search. Optional filters: shortest validity, least data (unlimited plans always qualify), unlimited data only. Cheapest first, at most 20; total says how many matched. Each plan carries its id (EAN), validity, data, networks per country, 5G, calls, SMS, phone number, whether it can be topped up, operator, price in the asked currency, and its page on simoptions.com, where it is bought.

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": {
      "destinations": "<destinations>"
    },
    "name": "plans_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
minDaysNoShortest validity accepted, in days.
currencyNoISO 4217 code of the currency the prices are in, e.g. "USD" or "EUR". Defaults to the site's own currency.
minDataGbNoLeast data accepted, in GB. Unlimited plans always qualify.
destinationsYesDestination codes from destinations_search ("FR", "EUR"). One code: the plans its page lists. Several: the plans that cover them all.
unlimitedOnlyNoOnly plans with unlimited data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, closed-world lookup, so the safety profile is covered. The description adds real operational context beyond that: results are cheapest-first, capped at 20, with a 'total' count for matches, prices returned in the requested currency, and unlimited plans always surviving a minDataGb filter. It does not address freshness or whether stock varies by region, which keeps it from a 5.

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?

Front-loads the core action and the single/multi-destination distinction, then filters, then ordering and return fields. It is dense rather than padded, though the final sentence enumerating every returned field is a long run-on that could be tightened.

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 no output schema, the description carries the burden of describing return values and does so thoroughly (id/EAN, validity, data, per-country networks, 5G, calls, SMS, phone number, top-up, operator, price, page URL). Combined with the 20-result cap and total count, an agent has everything needed to call and interpret results.

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%, so the schema already carries parameter meaning; the description only restates filters in prose ('shortest validity, least data (unlimited plans always qualify), unlimited data only') and the currency default. The multi-destination semantic is also already in the schema. Baseline 3 is appropriate since the description adds little beyond structured fields.

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 ('List the SimOptions travel eSIM plans in stock for a trip') and immediately disambiguates scope: single destination vs multiple destinations. An agent can tell this apart from destinations_search (which supplies the codes) and devices_check without reading either schema.

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 to destinations_search for obtaining destination codes, and explains the single-vs-multiple destination behavior plus what each filter means. It does not state exclusion cases (e.g. when to prefer devices_check, or what to do when zero plans match beyond the 'total' counter), so it stops short of full when/when-not guidance.

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