Skip to main content
Glama
Sign In

PuraSIM Travel eSIM MCP Server

by io.github.purasim
OverviewDiscussionsAdmin

Get destination coverage and networks

get_destination_info
Read-onlyIdempotent

Coverage (countries), mobile operators and network types (4G/5G), validity options and entry price of a PuraSIM destination.

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": "<destination>"
    },
    "name": "get_destination_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
destinationYesCountry name in any language (e.g. "Japan", "Japón"), ISO 3166 code (e.g. "JP"), region (e.g. "Europe", "Asia", "Balkans", "Global") or a destinationId returned by another tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety properties (read-only, idempotent, non-destructive, closed-world), and the description adds useful behavioral context by enumerating the information classes returned: coverage, operators, network types, validity, and entry price. It does not describe output format or currentness, but the annotations lower the transparency burden.

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 definition is a single tightly scoped sentence with no filler. The most important content—what data the tool returns—is front-loaded and immediately useful.

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 three-parameter read-only lookup tool with complete schema descriptions and clear annotations, the description is nearly sufficient: it enumerates the key information an agent would retrieve. The only gap is that it does not describe the shape of the returned data, but no output schema exists and the enumeration gives enough context to call the tool correctly.

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%, including full enum and format details for destination, locale, and currency. The description adds no parameter-level meaning beyond that, so the schema fully carries parameter semantics and the baseline score 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?

The description clearly states the resource and data scope: coverage countries, mobile operators, network types, validity options, and entry price for a PuraSIM destination. It is more specific than the title alone, but it does not explicitly distinguish itself from siblings like check_coverage or list_destinations.

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?

The description explains what information is available but gives no guidance on when to use this tool versus check_coverage, list_destinations, or search_plans. There are no prerequisites, exclusions, or alternative-selection cues, so the agent must infer usage from the sibling names.

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