Skip to main content
Glama

OsmO Travel eSIM

Show roaming vs eSIM card

show_roaming_comparison
Read-onlyIdempotent

Shows a carrier roaming pass next to the best eSIM option as an interactive card.

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

Input Schema

NameRequiredDescriptionDefault
daysYes
usageNo
dataGbNo
travellersNo
destinationYes
homeCarrierYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description's one contribution beyond that is that the result is an 'interactive card', implying a rendered UI payload rather than plain data — genuinely useful for an agent deciding whether to surface it. It says nothing, though, about how the 'best eSIM option' is chosen or what the card contains when optional inputs like usage/dataGb are omitted.

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?

A single 15-word sentence with the resource and output form front-loaded and no filler. It is efficient, but the brevity here is under-specification rather than disciplined concision.

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

Completeness2/5

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

A six-parameter tool with three required inputs, zero schema descriptions, and no output schema needs the description to explain inputs and result shape; instead it supplies one sentence. Given the near-identical sibling names, the missing differentiation alone is a material completeness gap for an agent selecting between tools.

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 (homeCarrier, destination, days, usage, dataGb, travellers), so the description carries the full burden of explaining them and adds essentially nothing. 'Carrier' loosely echoes homeCarrier and the comparison implies a destination, but there is no guidance on units, format, or how optional params (usage enum, dataGb, travellers) change the comparison. Only the enum parameter is self-explanatory from the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete output (a carrier roaming pass shown next to a 'best eSIM option' as an interactive card), which tells an agent this renders a UI comparison rather than returning raw data. However, it never distinguishes itself from the very similarly named siblings compare_roaming_vs_esim and show_esim_comparison, and 'best' is left undefined. An agent reading all three would have no basis for choosing this one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no exclusions, and no named alternative. The description does not say whether this should be called when the user has already accepted the roaming option, when they want a visual, or before/after compare_roaming_vs_esim. Usage must be inferred entirely from the name.

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