Skip to main content
Glama

OsmO Travel eSIM

Show eSIM plan cards

show_esim_plans
Read-onlyIdempotent

Shows eSIM plan options as interactive cards. Takes the same trip inputs as search_esim_plans plus the optionIds to show (a subset of its results; the order is always the published ranking).

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": {
      "trip": "<trip>"
    },
    "name": "show_esim_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
tripYes
limitNo
needsNo
usageNoPhone use if dataGb is unknown: light (~0.3 GB/day), moderate (~0.8), heavy (~2)
dataGbNoData needed per person in GB; omit to estimate from usage
optionIdsNo
unlimitedNotrue = only unlimited-data plans
travellersNoPeople travelling; each needs their own eSIM
maxPriceUsdNo
catalogVersionNocatalogVersion from the data tool result, so the card can say if prices changed

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 declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds two genuinely useful behavioral facts beyond that: the output is rendered as interactive cards rather than raw data, and the card order is always the published ranking and cannot be reordered.

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

Conciseness5/5

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

Two sentences, front-loaded with the core behavior, with the optionIds constraint and ordering guarantee packed into a single parenthetical. No redundant restatement of the name or title.

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?

This is a 10-parameter, nested-object rendering tool with no output schema, so the description must carry more weight. It says the output is cards but not what a card contains or what happens when optionIds reference stale catalog entries, and the interaction with limit or catalogVersion (price-change indicators) is unaddressed.

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?

With only 50% schema description coverage across 10 parameters, the description compensates partially: it explains that optionIds is a bounded subset of search results and that the trip object mirrors search_esim_plans. However, it leaves limit, maxPriceUsd, catalogVersion, needs and travellers entirely to the schema, and the delegation to "same trip inputs as search_esim_plans" only works if the agent already knows that tool.

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?

States a specific verb and resource ("Shows eSIM plan options as interactive cards") and distinguishes itself from search_esim_plans by requiring optionIds that are a subset of that tool's results. It does not contrast with the singular show_esim_plan or compare_esim_plans siblings, so differentiation is partial rather than complete.

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?

The ordering of operations is implied rather than stated: optionIds come from search_esim_plans results, so this is a follow-up rendering step. There is no explicit "use this when / use X instead" guidance and no statement of when the single-plan or comparison variants should be preferred.

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