Skip to main content
Glama

OsmO Travel eSIM

Compare roaming pass vs eSIM

compare_roaming_vs_esim
Read-onlyIdempotent

Use this when the user asks whether a travel eSIM is cheaper or better than their own mobile carrier's international roaming pass or plan for a trip to one destination, or about local SIM cards. Compares the carrier's published pass price with the eSIM plans in the OsmO catalogue. For multi-country trips, call it once per country.

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": {
      "homeCarrier": "<homeCarrier>",
      "destination": "<destination>",
      "days": "<days>"
    },
    "name": "compare_roaming_vs_esim"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYes
usageNo
dataGbNo
travellersNo
destinationYes
homeCarrierYes

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 this a safe, idempotent, closed-world read, so the bar is lower. The description still adds real context beyond them: the data sources are the carrier's published pass price and the OsmO catalogue, and multi-country comparisons require one call per country — behavior an agent could not infer from the annotations.

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 sentences, front-loaded with the trigger condition and followed by what is compared and the multi-country rule; nothing is redundant. The trailing 'or about local SIM cards' widens scope without explaining how local SIMs enter the comparison, which is the one mildly loose phrase.

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?

There is no output schema, and the description says nothing about what the comparison returns (price difference, recommendation, caveats) or about assumptions such as how travellers and data usage feed the estimate. For a six-parameter tool with zero schema description coverage, the definition leaves meaningful gaps.

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

Parameters2/5

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

Schema description coverage is 0% across six parameters, so the description must carry the burden and largely does not. It only implies homeCarrier and destination ('their own mobile carrier's ... plan', 'trip to one destination'); days, usage, dataGb, and travellers — including why the light/moderate/heavy enum matters for the price comparison — are never addressed.

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?

States a specific verb and resource: it compares the user's carrier's published roaming pass price against eSIM plans in the OsmO catalogue. The framing (carrier pass vs. eSIM) implicitly separates it from siblings like compare_esim_plans, which compares eSIM plans to one another, and an agent can route correctly from the description alone.

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?

Gives an explicit trigger — the user asks whether a travel eSIM is cheaper/better than their carrier's roaming pass, or asks about local SIM cards — plus a concrete operational rule for multi-country trips (call once per country). It stops short of naming a sibling to use instead when there is no home carrier to compare against, so it lacks true exclusions.

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