Skip to main content
Glama
Sign In

PuraSIM Travel eSIM MCP Server

by io.github.purasim
OverviewDiscussionsAdmin

Get a link to buy a plan on purasim.com

create_checkout_link
Read-onlyIdempotent

Return the purasim.com page of a plan with the plan preselected, where the user can review and buy it. No order is placed and no payment is made by this tool. With only a destination, the link opens the destination page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_checkout_link"
  }
}

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
planIdNo
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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine value by explicitly stating no order is placed and no payment is made, reinforcing that this is a non-mutating link generator. It stops short of describing the return type or any auth requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences with no filler, and the core purpose is front-loaded in the first sentence. The behavioral caveats follow logically without padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should confirm that the return value is a URL string, but it only implies a page/link without stating the return format. It also leaves planId semantics unexplained. Adequate but with clear gaps for a tool an agent must wire into a flow.

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 67%, with locale and destination well documented in the schema but planId undocumented anywhere. The description adds a small amount of destination-only behavior but says nothing about how planId affects the resulting link. Baseline 3 is appropriate given the partial coverage gap.

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 states a specific verb and resource: it returns the purasim.com page of a plan with the plan preselected. An agent understands this produces a purchase-page link rather than performing a transaction. It does not explicitly distinguish itself from siblings like get_plan or search_plans, 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?

The tool clarifies it places no order and takes no payment, which usefully rules out a purchase interpretation, and it explains behavior when only a destination is supplied. However, there is no guidance on when to choose this over get_plan or recommend_plan, leaving the selection decision to inference.

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