Skip to main content
Glama

Find Horizon destinations

search_destinations
Read-only

Finds Horizon's country, regional and global destinations by English name, slug or ISO country code, for a destination whose name is unclear or a trip through several countries. With coveringCountries (ISO-3 codes) it returns only the destinations that cover every country of the itinerary. Returns each destination's name, slug and type, without prices.

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
limitNo
queryNo
offsetNo
coveringCountriesNoISO-3 country codes, for example FRA and DEU.

Output Schema

NameRequiredDescriptionDefault
nextStepYes
nextOffsetYes
destinationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/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 useful behavior: coveringCountries returns only destinations covering every country of the itinerary, and results exclude prices. However, it remains silent on pagination behavior and total-result counts, which matter for a search tool with limit/offset.

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, front-loaded with the core purpose, then the country-coverage filter, then the return shape. Every sentence carries information an agent needs; nothing is repeated from the name.

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 annotations covering safety and an output schema presumably documenting the name/slug/type return, the description only needs to explain selection semantics, which it does. Minor omissions (pagination expectations, empty-result behavior) are the only remaining gap for a four-parameter search tool.

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 only 25%, and the description compensates for the weakest spots by explaining what query accepts (English name, slug, ISO code) and what coveringCountries means semantically. It says nothing about limit or offset, which are left to the schema's defaults and bounds, so the coverage gap is only partly closed.

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 pairs a specific verb ("Finds") with a precise resource ("Horizon's country, regional and global destinations") and names the match keys: English name, slug or ISO country code. That is enough to distinguish it from plan/coverage siblings, but it never explicitly contrasts itself with get_destination_coverage or list_destination_plans, so it stops short of full sibling differentiation.

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 supplies clear when-to-use context: a destination whose name is unclear, or an itinerary spanning several countries handled via coveringCountries. It gives no when-not-to-use or named alternative for looking up plans or coverage, so guidance is good but not complete.

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