Skip to main content
Glama

OsmO Travel eSIM

Show destination snapshot

show_destination_snapshot
Read-onlyIdempotent

Shows a compact mobile-data snapshot of one destination 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": {
      "destination": "<destination>"
    },
    "name": "show_destination_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
destinationYes

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, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description does add one piece of non-annotation context — that the result is rendered as an interactive card rather than raw data — which matters for an agent composing a UI response. It adds nothing about lookup failures, ambiguity in destination matching, or what the card shows.

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 front-loaded sentence with no filler; the resource is named first and the output form second. It is efficient, though brevity here edges into under-specification rather than tightness.

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?

With no output schema, the description is the only place an agent can learn what the card returns, and "compact mobile-data snapshot" is too vague to plan around. Combined with the undocumented destination format and no sibling differentiation, the definition leaves real gaps for a tool an agent must choose deliberately.

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% for the single required parameter, so the description carries the full burden and it does not meet it. It says "one destination" but never specifies whether the value is a city name, country, IATA code, or internal ID — a critical ambiguity given the 2–80 character constraint.

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?

"Shows a compact mobile-data snapshot of one destination" gives a verb and resource, and "as an interactive card" hints at a visual/UI output. But "snapshot" is never defined — an agent cannot tell whether it contains prices, coverage, plan options, or a summary card — and it never states how it differs from the closely named get_destination_guide sibling.

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 guidance on when to pick this over get_destination_guide, show_data_estimate, or show_esim_plans, all of which plausibly overlap. No prerequisites, no exclusions, no context about the destination lookup flow.

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