Skip to main content
Glama
Sign In

PuraSIM Travel eSIM MCP Server

by io.github.purasim
OverviewDiscussionsAdmin

Recommend an eSIM plan for a trip

recommend_plan
Read-onlyIdempotent

Recommend the best PuraSIM eSIM plan(s) for a trip, from its length in days and the expected data usage (light, medium or heavy). Accepts one destination or a list of countries visited on the same trip (it then looks for plans that cover all of them).

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": {
      "tripDays": "<tripDays>"
    },
    "name": "recommend_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
usageNolight: maps, messaging, email. medium: social media, browsing, some video. heavy: video streaming, video calls, hotspot.medium
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
tripDaysYes
countriesNoCountries visited on one trip, e.g. ["France", "Italy", "Switzerland"]. Use instead of destination for multi-country trips.
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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior. The description adds useful behavior beyond that: for a country list, it 'looks for plans that cover all of them.' It still does not describe ranking criteria or return details, so 4 rather than 5.

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 the purpose and compactly covering the key input scenarios. There is no filler or repetition.

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 6-parameter read-only recommendation tool with no output schema, the description covers input intent and multi-country behavior, while annotations cover safety. It does not explain what the recommended plan result contains, such as price or coverage details, leaving a minor completeness gap.

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?

With 83% schema description coverage, the schema already documents most parameters. The description adds meaning by stating the recommendation is driven by tripDays and usage, and that a countries list is treated collectively to find plans covering all visited countries; locale and currency are left to the schema.

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 ('Recommend') and resource ('PuraSIM eSIM plan(s)') for a trip, with the basis being trip length and data usage. It is clear, but it does not name or differentiate itself from siblings such as search_plans or get_plan, so it falls short of a 5.

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?

Implies usage when planning a trip with known length and expected data usage, and explains destination versus countries for multi-country trips. However, it never states when to prefer this over search_plans or when not to use it, and provides no explicit alternatives.

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