Skip to main content
Glama

List eSIM plans

list_plans
Read-onlyIdempotent

The plans on sale for a destination, with data, validity, networks and price in the requested currency. Unlimited plans give a daily amount at full speed, then a reduced speed.

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_id": "<destination_id>"
    },
    "name": "list_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOnly fixed data plans, only unlimited day passes, or all. Defaults to all.
currencyNoISO 4217 code for prices, e.g. EUR, GBP, JPY. Defaults to USD.
languageNoLanguage of the buy link and of region names: en, it, es, fr, de, pl, pt, tr. Defaults to en.
destination_idYesDestination id from search_destinations, e.g. "jp" or "eu-42".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is fully covered. The description adds genuine domain context the annotations cannot: that unlimited plans are throttled to a reduced speed after a daily full-speed allowance. It says nothing about result volume, ordering or pagination, so it is useful but not rich.

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?

Two sentences, front-loaded with what is returned and zero filler. The second sentence about unlimited throttling is the one piece of information that could not be guessed from the name or schema, so every sentence earns its place.

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?

For a read-only list tool with no output schema and fully documented parameters, the description covers what the results contain and how to interpret the unlimited-plan variant. Minor gaps remain on result ordering, pagination and empty-result behavior, but nothing blocks a correct call.

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%, with per-parameter descriptions for type, currency, language and destination_id including examples and defaults. The description only echoes currency ('price in the requested currency') and adds no semantics beyond the schema, so the baseline 3 applies.

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?

Conveys a specific resource and scope: the plans on sale for a given destination, with the fields returned (data, validity, networks, price). It never names how it differs from siblings like get_quote or search_destinations, so the agent must infer that this is the browse step rather than the pricing step.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or when-not-to-use guidance, and no alternative is mentioned. The required destination_id and the 'plans on sale' framing imply a browsing use case, but the agent is left to infer that this should precede get_quote rather than replace it.

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.