Skip to main content
Glama

esimdata: travel eSIM comparison

Get one eSIM plan

get_plan
Read-onlyIdempotent

Everything esimdata knows about one plan (by the id search_plans returned): all countries it covers, networks, policies, the provider's own page, the buy link and its price history.

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

Input Schema

NameRequiredDescriptionDefault
plan_idYesThe id exactly as search_plans returned it, e.g. "airalo:moshi-moshi-15days-5gb" (ids are provider:code and are not guessable).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / plan_id / description
      Previous value: -"A plan id such as \"airalo:jp-3gb\"."New value: +"The id exactly as search_plans returned it, e.g. \"airalo:moshi-moshi-15days-5gb\" (ids are provider:code and are not guessable)."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description earns credit by disclosing the breadth of the payload — including provider page, buy link and price history — which is behavioral context annotations cannot express, and it reinforces the key constraint that ids are sourced from a prior search. No mention of failure behavior for unknown ids.

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 well-formed sentence that front-loads the core purpose and then lists the return payload. No filler, no repetition, and the parenthetical id provenance is placed where it is most useful.

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 description correctly takes on the job of describing return contents, and it does so concretely. The only gap is edge-case behavior — what happens with an unknown or stale id — which for a simple single-param read tool is a minor omission.

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 100% and the schema itself documents the provider:code format and non-guessability. The description's phrase 'by the id search_plans returned' points to the id's provenance but largely restates what the schema already says, so it adds little beyond the structured field.

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?

The description names a single specific resource ('one plan') and enumerates exactly what it returns (countries, networks, policies, provider page, buy link, price history), which makes it instantly distinguishable from search_plans and compare_plans. An agent knows precisely what this call yields without opening the schema.

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?

It gives clear context for when to use it: immediately after search_plans, using an id that search_plans returned. It stops short of explicit alternatives or exclusions (e.g., that compare_plans should be used when evaluating multiple plans), so the routing guidance is clear but not fully bounded.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources