Skip to main content
Glama

Compare eSIM and roaming prices

compare_prices
Read-only

A price comparison for a trip from Ukraine: travel eSIMs from 12 providers (Tutu eSIM, Airalo, Yesim, Holafly, Nomad, Saily, Sparks and others) and Ukrainian operators' roaming (Kyivstar, Vodafone, lifecell), each price with its check date, cheapest first. Tutu eSIM is not always the cheapest and the answer says so.

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

Input Schema

NameRequiredDescriptionDefault
gbNoPlan size (default 5) or unl
daysNoTrip length: only plans valid at least this many days
countryYesISO 3166 code (EG, TR) or the name in English, Ukrainian or Russian

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 cover the safety profile (read-only, non-destructive, not open-world). The description adds genuine behavioral context beyond that: 12 providers are covered, every price carries a check date for freshness, results are ordered cheapest first, and it explicitly claims impartiality about Tutu eSIM. Missing only things like currency handling or staleness thresholds.

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

Conciseness3/5

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

The core comparison scope is front-loaded and dense with useful facts. The closing sentence about Tutu eSIM not always being cheapest reads as promotional framing rather than operational guidance, and the provider/operator list is lengthy. Structure is fine but the last sentence does not fully earn its place.

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 carries the burden of describing returns, and it does: providers, prices, check dates, cheapest-first ordering. Parameter behavior is covered by the schema. A brief note on currency or how many results to expect would complete it.

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 description coverage is 100%, so country, gb, and days are already fully documented, including the enum values and the 5GB default. The description adds no parameter-level meaning beyond implying a trip context. 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?

The description states a concrete verb and resource: a price comparison of travel eSIMs from named providers plus Ukrainian operators' roaming, sorted cheapest first. That is far more specific than the title alone. It does not explicitly distinguish itself from siblings like roaming_cost or search_plans, so it stops 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?

Usage is implied by the framing ('for a trip from Ukraine'), suggesting this is the combined eSIM-plus-roaming lookup. However, there is no explicit when-to-use or when-not-to-use guidance versus roaming_cost or search_plans, and no stated prerequisites.

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