Skip to main content
Glama
Sign In

PuraSIM Travel eSIM MCP Server

by io.github.purasim
OverviewDiscussionsAdmin

Check eSIM coverage in a country

check_coverage
Read-onlyIdempotent

Answer "does a PuraSIM eSIM work in ?". Without destination, lists every PuraSIM destination (country, regional or global plan) that covers the country. With destination, says whether that destination covers it and with which mobile networks.

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": {
      "country": "<country>"
    },
    "name": "check_coverage"
  }
}

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
countryYesCountry name in any language or ISO 3166 code.
currencyNoCurrency for prices. Checkout may show the shopper's local currency.USD
destinationNoCountry 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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds real value beyond them by disclosing outcome content: with a destination it reports coverage and the specific mobile networks, without one it enumerates every covering plan.

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?

Three compact sentences, front-loaded with the exact user question being answered, then the two branches. No filler or restatement of the title.

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?

There is no output schema, so the description must characterize returns — and it does, at the level of destinations, plans, coverage verdicts and mobile networks. It omits any mention of pricing despite a currency parameter, leaving a small gap about what else comes back.

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 baseline is 3. The description goes beyond it by explaining the semantic effect of supplying destination versus omitting it, which the schema only defines as an optional string.

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 in the user's own question form ("does a PuraSIM eSIM work in <country>?") and explains the two operating modes. It does not name a sibling, and its no-destination mode visibly overlaps with list_destinations without acknowledging the difference.

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?

Clearly splits usage into 'without destination' versus 'with destination' and says what each returns, which is actionable context. It stops short of routing the agent away from alternatives — notably it never says when to prefer this over list_destinations or get_destination_info, which cover adjacent ground.

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