Skip to main content
Glama

What roaming with a Ukrainian SIM will cost

roaming_cost
Read-only

The total in UAH for a trip's mobile data with a Ukrainian SIM (Kyivstar, Vodafone, lifecell): with no bundle, with the operator's best bundles, Kyivstar's «Travel SIM», compared with a Tutu eSIM, for one phone or the whole family. Every number from the operators' sites with its source and check date; when an operator option is cheaper than Tutu eSIM the answer says so. 25 destinations have operator prices; others only the eSIM.

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

Input Schema

NameRequiredDescriptionDefault
daysNoTrip length, 1–60 (default 7)
phonesNoPhones in the family, 1–5 (default 1)
countryYesISO 3166 code (EG, TR) or the name in English, Ukrainian or Russian
operatorNoDefault all
gb_per_dayNo0.5 maps and messengers, 1 + social media (default), 2 + video

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: figures come from the operators' sites with source and check date, and the answer explicitly flags when an operator option beats the Tutu eSIM. It does not discuss caching or staleness beyond the check date, which keeps it short of a 5.

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?

The core output (total in UAH) is front-loaded, and the remaining clauses carry real information rather than filler. The first sentence is dense and slightly run-on, which costs a point on readability.

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

Completeness5/5

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

There is no output schema, and the description compensates by describing what the answer contains: totals, bundle comparisons, eSIM comparison, per-source attribution with check dates, and a cheaper-operator flag. Combined with full schema coverage, an agent has enough to call this correctly and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema cannot: the 25-destination limit tells the agent when the operator dimension of the country parameter will actually produce comparisons. It also frames phones as 'one phone or the whole family', reinforcing the phones parameter's intent.

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 computation and resource: the total in UAH for a trip's mobile data on a Ukrainian SIM, covering no-bundle, operator bundles, Kyivstar Travel SIM and a Tutu eSIM comparison. An agent can tell this is a cost-estimation tool rather than a lookup or search tool. It never names a sibling (e.g. compare_prices), so sibling differentiation is only implicit.

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's mobile data with a Ukrainian SIM', but there is no explicit when-to-use or when-not guidance and no named alternative to route to. The one implicit routing hint is the coverage caveat: 25 destinations have operator prices, others only the eSIM.

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