Skip to main content
Glama
Sign In

PuraSIM Travel eSIM MCP Server

by io.github.purasim
OverviewDiscussionsAdmin

List eSIM destinations

list_destinations
Read-onlyIdempotent

List the destinations PuraSIM covers (countries, regions and global plans) with the entry price of each. Filter by type or name.

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

Input Schema

NameRequiredDescriptionDefault
typeNoOnly this kind of destination.
queryNoOnly destinations whose name contains this text.
localeNoLanguage of the user. Sets the language of the purasim.com pages returned (en, es, de, fr, it, pt, nl, pl, cs, da, no, sv, ro, tr, ar, he, id, ja, ko, th, zh) and of country names.en
currencyNoCurrency for prices. Checkout may show the shopper's local currency.USD

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 declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely beyond that by disclosing the payload shape (destinations plus entry price) and the scope of the catalog. It stops short of saying whether results are paginated or whether prices are starting-from versus exact, leaving a small gap.

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, no filler, with the core action and return content front-loaded before the filter hint. Every clause carries information an agent can act on.

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 does the necessary work of naming what comes back (destinations with entry price). All four parameters are optional and schema-documented, so the agent has what it needs to call correctly; only pagination behavior and result-size expectations are unaddressed.

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 enum values and defaults fully documented in the schema, so the baseline is 3. The description only loosely frames 'type' and 'name' as filters and adds nothing on the locale or currency parameters beyond what the schema already states.

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 ('List the destinations PuraSIM covers'), enumerates the three destination kinds, and notes that each entry carries an entry price. It is clearly distinguishable from get_destination_info and search_plans by being the catalog-wide listing, though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

The phrase 'Filter by type or name' implies when the filters apply but gives no explicit when-to-use or when-not-to-use guidance. There is no routing to get_destination_info for details, check_coverage for coverage verification, or search_plans for plan-level search, despite those being adjacent siblings.

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

All PuraSIM Travel eSIM MCP Server toolsInspect
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