PuraSIM Travel eSIM MCP Server

Search eSIM plans

search_plans

Read-onlyIdempotent

Search PuraSIM travel eSIM data plans for a destination (country, region or global), cheapest first. Optional filters on price, data, validity and daily plans. Every plan includes a purasim.com link where the user can buy it.

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": "search_plans"
  }
}

Input Schema

Name	Required	Description	Default
`sort`	No		price
`limit`	No
`locale`	No	Language 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
`currency`	No	Currency for prices. Checkout may show the shopper's local currency.	USD
`maxPrice`	No	Maximum price in the chosen currency.
`minDataGB`	No	Minimum total data in GB (for daily plans: GB per day × days).
`unlimited`	No	true: only daily plans, which keep working at reduced speed after the daily allowance. false: only plans with a fixed data total.
`destination`	Yes	Country 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.
`maxValidityDays`	No
`minValidityDays`	No	Minimum validity in days, usually the trip length.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive and closed-world behavior, so the description adds the useful extras: results are ordered cheapest-first and every plan carries a purasim.com purchase link. It stops short of describing pagination or how limit interacts with result counts.

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 short sentences: what it searches and how results are ordered first, filters second, and the purchase-link return detail last. No filler or restatement of the tool name.

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 10 parameters and no output schema, the description supplies the key return-value fact (each plan has a buy link) and the ordering, which is what an agent most needs. Minor gaps remain around the default limit of 10 / max 30 and the shape of plan objects.

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 coverage is 70% and the schema itself explains destination, locale, currency, minDataGB, unlimited and validity fields well. The description only summarizes the filter families at a high level, adding no semantics beyond what the schema already documents; baseline 3 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?

Specific verb and resource ("Search PuraSIM travel eSIM data plans") plus the accepted destination shapes (country, region, global) and default ordering. It does not explicitly distinguish itself from siblings like get_plan or recommend_plan, so an agent must infer the boundary.

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?

"Optional filters on price, data, validity and daily plans" implies a browsing/filtering use case, but there is no explicit statement of when to pick this over recommend_plan or get_plan. Usage is implied rather than directed.

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 tools Inspect

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.