Skip to main content
Glama

search_itineraries

Read-onlyIdempotent

Search vetted multi-day itineraries (routes) curated from destination sources.

ONLY call this when the traveler has named a specific Icelandic region and you
want a pre-vetted route for it. This is not a general trip-planning tool and it
has no opinion about where someone should go: coverage is a handful of regions,
so treating it as "show me an itinerary" produces a route for the wrong part of
the country. Without a region it returns nothing, by design. When it returns
nothing, compose the itinerary yourself — that is the expected path, not a
failure, and it is always better than offering a route for a region the traveler
did not ask about.

Each itinerary returns ordered, geocoded key_stops plus the route's travel scale
(duration_days, total_distance_km, and a summary that flags long driving distances).
To build a bookable trip, take each stop's latitude/longitude and call
search_operators(latitude, longitude, radius_km) near it (or use
search_operators_near_itinerary to do every stop in one call). Itineraries are
operator-agnostic: they describe a route, never specific operators.

PLAN FROM THE ARRIVAL POINT, not the first stop. Most tourists fly into
Keflavik (KEF) and start near Reykjavik, so a route that begins in a far region
(the Westfjords stops below start at Holmavik, ~5 hours from Reykjavik) needs the
drive from Reykjavik to the first stop and back to departure built into the plan.
Use total_distance_km and the "long, slow roads" note to set realistic daily
pacing; never present the route as if the tourist were already at stop one.

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_itineraries"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoREQUIRED to get results. The Icelandic region the traveler asked about, e.g. 'Westfjords', 'North', 'South'. Omit it and this tool deliberately returns nothing: curated routes exist for only a few regions and must never be offered for a trip somewhere else.
seasonNoFilter by season, e.g. 'summer', 'winter', 'all-year'.
travel_modeNoFilter by travel mode, e.g. 'self-drive'.
max_duration_daysNoOnly itineraries that fit within this many days.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare it a read-only, idempotent, closed-world search, but the description adds non-obvious behavior: an omitted region deliberately returns zero results rather than a default list, empty results are an expected path rather than a failure, and itineraries are operator-agnostic. It also describes the returned payload (ordered geocoded key_stops, duration_days, total_distance_km, a long-drive warning summary) beyond what the safety annotations convey.

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?

Purpose and the when-to-call constraint are front-loaded, and the paragraph ordering (what it is → when to call → what it returns → how to build on it → planning caveat) is logical. It runs longer than a pure search tool needs and restates the 'don't offer the wrong region' point twice, but the later sections carry genuinely actionable orchestration guidance rather than filler.

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?

Even though an output schema exists, the description covers the two things the schema cannot: the deliberate empty-result behavior and the multi-step workflow of pairing each geocoded stop with operator search. For a zero-required-parameter, region-scoped lookup with a known failure mode, nothing an agent needs in order to call it correctly and interpret the result is missing.

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 and the schema already documents season, travel_mode and max_duration_days — the description says nothing about those three. It does, however, deepen the critical `region` parameter well past its schema text, explaining that omitting it yields no results by design and that a wrong-region match is worse than no match.

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?

The first sentence names a specific verb and resource — 'search vetted multi-day itineraries (routes) curated from destination sources' — and immediately scopes it to a narrow Icelandic region-based catalog. The follow-up paragraph explicitly contrasts it with general trip planning and, via the cross-references, with search_operators, so an agent can separate it from the operator-search siblings without reading schemas.

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

Usage Guidelines5/5

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

It gives an explicit trigger ('ONLY call this when the traveler has named a specific Icelandic region'), an explicit anti-pattern ('this is not a general trip-planning tool', do not treat it as 'show me an itinerary'), and a named fallback: compose the itinerary yourself when nothing is returned. It also routes the agent onward to search_operators/search_operators_near_itinerary for the booking step.

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