Skip to main content
Glama

OsmO Travel eSIM

Get destination eSIM guide

get_destination_guide
Read-onlyIdempotent

Use this when the user asks what to know about mobile data in one country: networks, 5G listed by plans, ID checks, typical plan prices, and researched local rules. Also accepts 'at sea' for cruises.

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

Input Schema

NameRequiredDescriptionDefault
destinationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 covered. The description adds value by revealing that the response is researched background content rather than live carrier data, but says nothing about data freshness, caching, or limitations for countries with thin coverage.

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 compact sentences, trigger first, special-case caveat last. The content enumeration is dense but each item carries routing value. No filler or repetition.

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 one-parameter read-only lookup with full annotation coverage and no output schema, the description covers purpose, trigger, content scope, and a non-obvious input case. Remaining gaps are the expected destination string format and the reliability/researched nature of the returned rules.

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?

Schema description coverage is 0% – the single required parameter is only typed as a 2-80 character string with no description. The description partially compensates by implying a single country and disclosing the special accepted value 'at sea', which the schema does not. However, it never says whether to pass a country name, ISO code, or demonym, leaving a real ambiguity on the one required field.

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?

The description names the resource precisely and enumerates the content delivered: networks, 5G by plan, ID checks, typical prices, and researched local rules. That content set is distinct enough from siblings like get_esim_plan or show_destination_snapshot that an agent can route correctly, though no sibling is named explicitly as a contrast.

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

Usage Guidelines4/5

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

The trigger is explicit: 'Use this when the user asks what to know about mobile data in one country.' It also carves out a special case ('at sea' for cruises), which is genuine when-to-use guidance. It stops short of naming a competing tool or stating when not to use it.

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