Skip to main content
Glama

Search eSIM destinations

search_destinations
Read-onlyIdempotent

Find the countries and regions Wigoo sells travel eSIMs for, with the starting price and a buy link. Search by country or region name in English, or by ISO country code. Without a query it returns the popular destinations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_destinations"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoCountry or region name in English, or ISO code: "Japan", "JP", "Europe".
currencyNoISO 4217 code for prices, e.g. EUR, GBP, JPY. Defaults to USD.
languageNoLanguage of the buy link and of region names: en, it, es, fr, de, pl, pt, tr. Defaults to en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 genuinely new behavioral information beyond them: the response includes a starting price and a buy link, and an empty query falls back to a popular-destinations list rather than erroring.

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?

Three short sentences with no filler: capability and return payload first, accepted query forms second, default behavior third. Every sentence carries distinct information and nothing is repeated from the schema.

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?

With no output schema, the description correctly shoulders the burden of describing the return payload (price, buy link) and does so. It does not indicate whether the results list is bounded or paginated, which is the one remaining gap for a search tool.

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 100%, so the baseline is 3, but the description adds semantics the schema omits: that the optional 'query' parameter, when absent, returns popular destinations instead of an empty result. It also reiterates the accepted input forms (English name or ISO code) in agent-facing language; currency and language defaults are left to the schema.

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 gives a specific verb and resource ("Find the countries and regions Wigoo sells travel eSIMs for") plus the payload (starting price and buy link). It is clearly distinguishable from list_plans or get_quote, but it never explicitly contrasts itself with get_destination, so sibling routing is only inferable from the plural/search framing.

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?

It states two concrete usage modes: searching by English name or ISO code, and browsing popular destinations when no query is supplied. That is clear context for when to call it, but there are no exclusions or named alternatives (e.g. use get_destination for a single known destination).

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.