Skip to main content
Glama

esimdata: travel eSIM comparison

eSIM market for a country

country_overview
Read-onlyIdempotent

A destination at a glance: how many plans and providers, the cheapest plan, the cheapest per GB, which mobile networks the providers say they use there, and pay-as-you-go eSIMs billed per MB (no bundle).

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": {
      "country": "<country>"
    },
    "name": "country_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesDestination: English name ("Japan"), ISO code ("JP") or common alias ("UK").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already carry the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the shape of what comes back: counts, cheapest plan, cheapest per GB, network claims, and per-MB billing products. That return-content disclosure matters because there is no output schema. It stops short of noting cost, pagination, or how "cheapest" is computed across currencies.

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?

One sentence, front-loaded with the framing phrase before the enumeration of outputs. The list is long but each item conveys distinct return data, so nothing is clearly padding; a slightly tighter grouping of the two cheapest-* items would help.

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 must convey what the aggregate returns, and it does list the main components. For a single-parameter read-only overview tool this is nearly sufficient; the only gap is ambiguity about the sibling relationship and about how the cheapest metrics are derived.

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 country parameter already documents English names, ISO codes, and aliases, so the baseline is 3. The description adds only the word "destination" and no extra syntax or normalization rules beyond what the schema states.

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?

"A destination at a glance" plus an explicit enumeration of the aggregate contents (plan/provider counts, cheapest plan, cheapest per GB, claimed networks, per-MB PAYG eSIMs) makes the verb and resource unambiguous. It does not name or contrast with siblings such as compare_plans or search_plans, so the boundary relies on the phrase "at a glance" rather than an explicit statement.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The agent must infer from "at a glance" that this is the cheap summary call and that search_plans/compare_plans are for detailed lookups, which is implied rather than stated.

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