Skip to main content
Glama

OsmO Travel eSIM

Show eSIM comparison

show_esim_comparison
Read-onlyIdempotent

Shows two to four eSIM plans side by side as an interactive card. Takes planIds 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": {
      "planIds": "<planIds>"
    },
    "name": "show_esim_comparison"
  }
}

Input Schema

NameRequiredDescriptionDefault
tripNo
usageNo
dataGbNo
planIdsYes
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

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds that the output is an interactive comparison card, which is genuinely useful output-shape context, but says nothing about how the optional trip/usage/dataGb inputs change the card or what happens if planIds are stale.

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?

Two tight sentences, front-loaded with what the tool produces and followed by the input source. No filler, though 'as an interactive card' is the only phrase conveying output form and could carry slightly more weight.

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?

Five parameters with a nested trip object and only 20% schema coverage, yet the description explains just one of them. For a card-rendering tool whose optional context parameters presumably shape the comparison, an agent gets no guidance on whether trip, usage, or dataGb are needed.

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 only 20% across 5 parameters, including a nested trip object with legs, dates and totalDays that the description never addresses. The one hint given — 2 to 4 plans and the origin of planIds — largely repeats what the schema already enforces via minItems/maxItems, and trip, usage, and dataGb are left unexplained.

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 two to four eSIM plans side by side as an interactive card'), which clearly distinguishes it from single-plan siblings like show_esim_plan. It does not differentiate itself from compare_esim_plans or the plural show_esim_plans, so the sibling boundary stays partly blurred.

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?

'Takes planIds from search_esim_plans' establishes a useful prerequisite and sequencing rule. However, it never says when to pick this over compare_esim_plans or show_esim_plans, nor any conditions under which a comparison should not be shown.

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