Skip to main content
Glama
Sign In

PuraSIM Travel eSIM MCP Server

by io.github.purasim
OverviewDiscussionsAdmin

Get eSIM plan detail

get_plan
Read-onlyIdempotent

Full detail of one PuraSIM plan by its planId (as returned by search_plans or recommend_plan): coverage, mobile networks, data, validity, price and purchase link.

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": {
      "planId": "<planId>"
    },
    "name": "get_plan"
  }
}

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
planIdYes
currencyNoCurrency for prices. Checkout may show the shopper's local currency.USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the safety profile is covered. The description earns credit by disclosing the return payload (including a purchase link) in the absence of an output schema, giving the agent an expectation of what data it gets back.

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?

A single front-loaded sentence with no filler: the resource and key appear first, followed by the returned fields. Nothing is restated from annotations or schema.

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 enumerated return fields are essential and present, and the planId provenance is explained. Minor gap: no indication of error/empty behavior for an invalid or expired planId in a closed-world catalog.

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?

The schema documents locale and currency thoroughly but leaves planId undocumented; the description fills exactly that gap by tying planId to the identifier returned by search_plans or recommend_plan. The enum/default behavior of the other two parameters is left to the schema, which is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (retrieve full detail) and resource (one PuraSIM plan) and names the scoping key (planId). It also enumerates what the detail contains — coverage, networks, data, validity, price, purchase link — so an agent can tell exactly what this returns versus list-oriented siblings like search_plans.

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?

The parenthetical '(as returned by search_plans or recommend_plan)' establishes the workflow position — this is the drill-down step after discovery — and implicitly distinguishes it from the discovery siblings. It stops short of explicit when-not guidance or stating what happens with an unknown planId.

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