Skip to main content
Glama

OsmO Travel eSIM

Show eSIM plan card

show_esim_plan
Read-onlyIdempotent

Shows one eSIM plan as an interactive card. Takes a planId from search_esim_plans.

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": {
      "planId": "<planId>"
    },
    "name": "show_esim_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
planIdYes
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
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so safety is covered. The description adds useful context that the result is an interactive card, but says nothing about what the card shows, whether it can drive follow-up actions, or how a stale catalogVersion manifests.

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 short sentences, front-loaded with the action and resource, with no filler. Every clause carries information the agent did not already have.

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?

For a simple two-parameter read-only card renderer with annotations and no output schema, the definition covers the essentials: single-plan scope and parameter provenance. It falls short only on how the card differs from a plain plan fetch, which would help an agent choose correctly.

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 only 50%, but the description compensates for the undocumented required parameter by naming its source (search_esim_plans), which the schema does not. catalogVersion is left entirely to its schema description, which handles it adequately.

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 one eSIM plan") and adds a rendering qualifier ("as an interactive card") that hints at output form rather than raw data. It does not explicitly contrast with get_esim_plan, so sibling differentiation is only partial.

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 clause "Takes a planId from search_esim_plans" gives a concrete upstream dependency, which is real usage guidance. However, it never states when to choose this card view over get_esim_plan or the show_*/compare_* siblings, so the when-to-use versus alternatives remains implicit.

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