Skip to main content
Glama

Search the travel guides

search_guides
Read-onlyIdempotent

Search every Meridian Dispatch travel guide by keyword: long-form dispatches, multi-day itineraries, country and town guides, venues (sights, museums, beaches, parks), trails and scenic drives, events and ski resorts. Use it first when you do not know the exact page. Once you know the place, read it in full with get_destination (a country or town), get_place (one sight, trail, event or ski resort) or get_dispatch (a dispatch or itinerary); for ranked top-ten lists use list_best_places, for a month use get_best_time. Returns up to limit pages ranked by relevance, each with its type, title, country, town, a one-line summary, a citable URL and when it was last updated. Ranking is keyword-based with travel synonyms; a country or month named in the query is honoured. Read-only. When nothing matches it returns an error message; retry with a broader query or a place name.

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

Input Schema

NameRequiredDescriptionDefault
typeNoReturn only one kind of page: dispatch (a reported long-form piece), itinerary (a multi-day country route), country or town (destination guides), town_compare (the towns of one country compared as places to stay, by need), venue (one sight), trail (a hike or scenic drive), event (a festival), ski_resort, museum (must-see works with their rooms and floors) or airport (how to get from the terminal to each town, airlines and routes, security, food, layovers). Omit to search all kinds.
limitNoMost results to return, 1 to 20. Defaults to 8.
queryYesWhat the traveller wants, in plain words: a place name ("Kotor"), an activity and a place ("glacier hike Iceland") or a theme ("festivals in Japan").
regionNoOnly this part of the world. Use it for asks like "festivals in Europe"; country is more precise when the traveller names one.
countryNoReturn only pages in this country, by English name, e.g. "Iceland". Omit to search worldwide.

Output Schema

NameRequiredDescriptionDefault
resultsNoMatching pages, best first.
attributionNoThe terms for quoting these pages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"Return only one kind of page: dispatch (a reported long-form piece), itinerary (a multi-day country route), country or town (destination guides), venue (one sight), trail (a hike or scenic drive), event (a festival), ski_resort, museum (must-see works with their rooms and floors) or airport (how to get from the terminal to each town, airlines and routes, security, food, layovers). Omit to search all kinds."New value: +"Return only one kind of page: dispatch (a reported long-form piece), itinerary (a multi-day country route), country or town (destination guides), town_compare (the towns of one country compared as places to stay, by need), venue (one sight), trail (a hike or scenic drive), event (a festival), ski_resort, museum (must-see works with their rooms and floors) or airport (how to get from the terminal to each town, airlines and routes, security, food, layovers). Omit to search all kinds."
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "dispatch",
      -  "itinerary",
      -  "country",
      -  "town",
      -  "venue",
      -  "trail",
      -  "event",
      -  "ski_resort",
      -  "museum",
      -  "airport"
      -]New value: +[
      +  "dispatch",
      +  "itinerary",
      +  "country",
      +  "town",
      +  "town_compare",
      +  "venue",
      +  "trail",
      +  "event",
      +  "ski_resort",
      +  "museum",
      +  "airport"
      +]
    • changedOutput schema / properties / results / items / properties / type / enum
      Previous value: -[
      -  "dispatch",
      -  "itinerary",
      -  "country",
      -  "town",
      -  "venue",
      -  "trail",
      -  "event",
      -  "ski_resort",
      -  "museum",
      -  "airport"
      -]New value: +[
      +  "dispatch",
      +  "itinerary",
      +  "country",
      +  "town",
      +  "town_compare",
      +  "venue",
      +  "trail",
      +  "event",
      +  "ski_resort",
      +  "museum",
      +  "airport"
      +]
  2. Changed3 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"Return only one kind of page: dispatch (a reported long-form piece), itinerary (a multi-day country route), country or town (destination guides), venue (one sight), trail (a hike or scenic drive), event (a festival), ski_resort or museum (must-see works with their rooms and floors). Omit to search all kinds."New value: +"Return only one kind of page: dispatch (a reported long-form piece), itinerary (a multi-day country route), country or town (destination guides), venue (one sight), trail (a hike or scenic drive), event (a festival), ski_resort, museum (must-see works with their rooms and floors) or airport (how to get from the terminal to each town, airlines and routes, security, food, layovers). Omit to search all kinds."
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "dispatch",
      -  "itinerary",
      -  "country",
      -  "town",
      -  "venue",
      -  "trail",
      -  "event",
      -  "ski_resort",
      -  "museum"
      -]New value: +[
      +  "dispatch",
      +  "itinerary",
      +  "country",
      +  "town",
      +  "venue",
      +  "trail",
      +  "event",
      +  "ski_resort",
      +  "museum",
      +  "airport"
      +]
    • changedOutput schema / properties / results / items / properties / type / enum
      Previous value: -[
      -  "dispatch",
      -  "itinerary",
      -  "country",
      -  "town",
      -  "venue",
      -  "trail",
      -  "event",
      -  "ski_resort",
      -  "museum"
      -]New value: +[
      +  "dispatch",
      +  "itinerary",
      +  "country",
      +  "town",
      +  "venue",
      +  "trail",
      +  "event",
      +  "ski_resort",
      +  "museum",
      +  "airport"
      +]
  3. Changed1 schema field changed
    • addedInput schema / properties / region
      Added value: +{
      +  "description": "Only this part of the world. Use it for asks like \"festivals in Europe\"; country is more precise when the traveller names one.",
      +  "enum": [
      +    "Europe",
      +    "Asia",
      +    "Middle East",
      +    "Africa",
      +    "North America",
      +    "Central America and the Caribbean",
      +    "South America",
      +    "Oceania"
      +  ],
      +  "type": "string"
      +}
  4. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations it discloses the ranking model (keyword-based with travel synonyms), that a country or month in the query is honoured, that results cap at `limit`, and — importantly — the failure mode: no matches returns an error, so retry with a broader query or place name. That error/retry behavior is the kind of detail annotations cannot 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?

Front-loaded with the core action and searchable corpus, then a compact routing clause for alternatives. It is dense but nearly every clause carries routing or behavior information; the standalone "Read-only." sentence duplicates readOnlyHint and is the one piece of dead weight.

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?

For a five-parameter search with an output schema and full annotation coverage, the description leaves nothing essential unanswered: what it searches, how results rank, what happens on empty results, and which sibling to use instead. Return-field descriptions are technically redundant with the output schema but harmless.

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 enum meanings for type, region and the limit bounds are already fully documented; the description does not need to repeat them. It does add one genuinely new semantic point — that a country or month named inside the free-text `query` is recognised — which is not evident from the schema alone.

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?

States a specific verb and resource ("Search every Meridian Dispatch travel guide by keyword") and enumerates exactly what is searchable — dispatches, itineraries, country/town guides, venues, trails, events, ski resorts. It immediately distinguishes itself from the retrieval siblings by naming them and their resource types.

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?

Gives an explicit trigger ("Use it first when you do not know the exact page") and then routes to the correct alternative in every identified case: get_destination for countries/towns, get_place for single sights/trails/events/resorts, get_dispatch for dispatches/itineraries, list_best_places for ranked lists, get_best_time for a month. Both when-to-use and when-not-to-use are covered.

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