SimFuse eSIM Storefront

List eSIM plans

list-plans

Read-onlyIdempotent

Show the eSIM plans on sale for one country or region, or search the whole catalog, narrowing by data allowance, validity and price. Use destination with a country code from list-destinations, or region with a slug from list-regions; never both. Use it when the traveller wants to compare what is available or find a plan inside a budget. Prices are live retail prices in the currency you ask for. For a trip covering two or more countries, use plan-trip first: it compares one plan for the whole route against one plan per country and picks the cheapest complete answer. Pass a plan id from here to get-plan, get-plan-coverage or create-checkout-session. Read-only, and it answers from the SimFuse catalog alone.

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": "list-plans"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Optional. Maximum plans to return, 1 to 100. Defaults to 25.
`region`	No	Optional. Canonical region slug, e.g. "europe", "southeast-asia" or "global", to search that regional shelf. Cannot be combined with destination. Unknown regions return no plans.
`currency`	No	Optional. ISO 4217 three-letter code prices are quoted and filtered in, e.g. "USD", "EUR", "GBP". Defaults to EUR. An unknown code falls back to EUR rather than failing.
`destination`	No	Optional. ISO 3166-1 alpha-2 destination country code, e.g. "US", "GB", "DE". Look it up with list-destinations rather than guessing. Cannot be combined with region. Omit both destination and region to search the whole catalog.
`max_price_cents`	No	Optional. Only plans at or below this retail price, in minor units (cents) of `currency`: 2500 is 25.00.
`min_price_cents`	No	Optional. Only plans at or above this retail price, in minor units (cents) of `currency`: 500 is 5.00.
`max_validity_days`	No	Optional. Only plans valid for at most this many days.
`min_validity_days`	No	Optional. Only plans valid for at least this many days, e.g. 14 for a two-week trip.
`max_data_amount_mb`	No	Optional. Only plans with at most this much data, in megabytes.
`min_data_amount_mb`	No	Optional. Only plans with at least this much data, in MEGABYTES: 1 GB is 1024, 10 GB is 10240.

Output Schema

Name	Required	Description
`plans`	Yes	The matching plans. Empty when nothing matched.
`matched`	Yes	How many plans matched the filters, before `limit` was applied.
`currency`	Yes	ISO 4217 code every price below is quoted in, e.g. "EUR".
`returned`	Yes	How many plans are in this response.
`truncated_by_candidate_cap`	Yes	True when a catalog-wide search hit its internal candidate cap, so there are further matches this call could not see. Narrow it with a destination or a tighter data or validity filter rather than assuming you have seen everything.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.7/5.0

Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive, non-open-world behavior. The description adds useful context beyond them: prices are live retail prices in the requested currency, results come from the SimFuse catalog alone, and destination/region cannot be combined. It is not a full behavioral disclosure, but with annotations covering safety it is strong.

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 core action and scope are front-loaded, followed by parameter routing, use cases, alternatives, and follow-up tools. For a 10-parameter catalog-search tool with many siblings, the length is appropriate and nearly every sentence carries selection or invocation guidance.

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?

Given the rich input schema, output schema, annotations, and 14 sibling tools, the description covers what the tool does, when to use it, how to choose destination versus region, how multi-country trips should route, and which tools consume plan ids. Nothing material is missing for correct selection and invocation.

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 baseline is 3. The description still adds meaning by telling the agent to source destination codes from list-destinations and region slugs from list-regions, and by stating that destination and region are mutually exclusive and that omitting both searches the whole catalog.

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?

The description uses a specific verb and resource: it shows or lists eSIM plans, either for a country/region or across the whole catalog, with filters. It clearly distinguishes this broad catalog search from plan-trip, get-plan, and get-plan-coverage, so an agent can select it without opening sibling schemas.

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?

It gives explicit selection conditions: use it when the traveller wants to compare availability or find a plan inside a budget. It also names alternatives and routing rules: use plan-trip first for multi-country trips, and pass a returned plan id to get-plan, get-plan-coverage, or create-checkout-session.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SimFuse eSIM Storefront tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?