Skip to main content
Glama

Search destinations

destinations_search
Read-only

Find the destinations SimOptions sells travel eSIMs for, by country or region name in any language, or by code. Returns up to 10 destinations, best match first: each one's code (pass it to plans_find), name, type (country or region), the countries it covers and its page on simoptions.com. A country with no page of its own is answered with the regional plans that cover it.

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": {
      "query": "<query>"
    },
    "name": "destinations_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesCountry or region name in any language, or its code: "Japan", "Europe", "JP". At least 2 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds value beyond them with a result cap ("up to 10"), ordering ("best match first"), and the non-obvious fallback that a country with no page is answered with covering regional plans. It does not cover empty-result or invalid-query behavior, which keeps it from a 5.

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 sentences, front-loaded with purpose then result shape then the fallback rule, with no filler. The enumeration of returned fields is justified because there is no output schema to carry it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one required string, no nesting), and with no output schema the description voluntarily documents the return shape, result limit, ordering and the no-page fallback. An agent has everything needed to call it and interpret the result.

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 coverage is 100% and the single parameter is documented with its own examples ("Japan", "Europe", "JP"), so the description's "by country or region name in any language, or by code" largely restates the schema. It adds little syntax or format meaning beyond what is already structured.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Find the destinations SimOptions sells travel eSIMs for" is a specific verb plus a precisely scoped resource, and the description narrows the lookup keys (country/region name in any language, or code). The parenthetical routing cue "pass it to plans_find" makes the boundary with the sibling explicit.

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 the two input keys and shows the chained workflow by naming plans_find as the consumer of the returned code, which is genuine usage context. It stops short of explicit exclusions (e.g. when to call plans_find or devices_check directly), so it is clear context rather than full when/when-not guidance.

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