Skip to main content
Glama

Browse the live Simcardo eSIM catalogue

list_esim_plans
Read-onlyIdempotent

Browse every current public plan, optionally by country/territory market (e.g. JP), package slug (e.g. europe-extra), or exact SKU. Returns localized links, retail total, coverage codes, validity and supplier facts, including explicit unknowns. Browse results are not travel recommendations; use quote_travel_esim to verify trip requirements. Paginate with next_after_sku.

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_esim_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuNoExact SKU to retrieve; do not use with market or after_sku.
marketNoMarket returned by list_esim_destinations. Omit to browse all markets.
currencyNoEUR
languageNoStorefront language for localized destination names, price display and links. Reply to the traveler in their language.en
after_skuNoCopy next_after_sku from the previous page, with the same filters.
page_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world browsing, so the bar is lower; the description still adds real context by enumerating returned facts (localized links, retail total, coverage codes, validity, supplier facts, explicit unknowns) and describing cursor pagination. It stops short of mentioning rate limits or result-count limits, which keeps it off 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?

Filter options are front-loaded, then return shape, then the routing caveat and pagination — a sensible order with no filler sentences. The single dense return-facts clause is long but every element (links, price, coverage, validity, supplier facts, unknowns) is distinct information.

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

Completeness4/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 correctly takes on the burden of describing return contents and includes pagination, exclusivity and alternative-tool guidance for a 6-parameter open-world browse tool. The gap is the unsupported 'package slug' filter and no mention of how currency/language behave beyond the schema defaults.

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?

It adds useful example values (JP for market, exact SKU) and reiterates cursor pagination, but it advertises filtering by "package slug (e.g. europe-extra)" while the schema exposes no slug parameter — only sku, market, after_sku and page_size. That phantom filter can mislead an agent into passing an unsupported argument, offsetting the example-value benefit at 67% schema coverage.

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?

"Browse every current public plan" gives a specific verb and resource, and the optional filters (market, SKU) plus the returned fields scope it precisely. It also names the sibling it is not — quote_travel_esim — so an agent can separate browsing from trip quoting without opening 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 states the exclusion ("Browse results are not travel recommendations") and routes to quote_travel_esim for trip verification, plus gives a pagination recipe via next_after_sku. It does not say when to prefer list_esim_destinations for discovery, but the market parameter's schema text covers that hand-off.

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