Meridian Dispatch

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.

Input Schema

Name	Required	Description
`type`	No	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.
`limit`	No	Most results to return, 1 to 20. Defaults to 8.
`query`	Yes	What the traveller wants, in plain words: a place name ("Kotor"), an activity and a place ("glacier hike Iceland") or a theme ("festivals in Japan").
`region`	No	Only this part of the world. Use it for asks like "festivals in Europe"; country is more precise when the traveller names one.
`country`	No	Return only pages in this country, by English name, e.g. "Iceland". Omit to search worldwide.

Output Schema

Name	Required	Description	Default
`results`	No	Matching pages, best first.
`attribution`	No	The terms for quoting these pages.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

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

AddedOct 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, and the description goes further than they do: ranking is keyword-based with travel synonyms, a country or month named in the query is honoured, results are capped at `limit` and ranked by relevance, and a no-match returns an error. That is real behavioral disclosure beyond the structured metadata.

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 routing rule and alternative-tool mapping in two dense sentences; the return-shape and error-handling sentences earn their place. Slightly long, and "Read-only" restates the annotations, but overall efficient with no 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?

For a five-parameter, multi-sibling search tool with full schema coverage and an output schema, the description covers routing, scope, ranking, result shape and failure recovery. An agent has everything needed to select and invoke it without opening the schemas.

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 100%, so the enum values for `type` and `region` and the bounds on `limit` are already fully documented in the schema. The description only adds the ranking nuance (country or month named in the query is honoured) and the limit/ranking behavior, which is marginal over the schema. Baseline 3 applies.

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 precise verb (search) and resource (travel guides), then enumerates the content types covered (dispatches, itineraries, country/town guides, venues, trails, events, ski resorts). It explicitly differentiates from siblings by naming get_destination, get_place, get_dispatch, list_best_places and get_best_time with the conditions that select each.

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 when-to-use rule ("use it first when you do not know the exact page") and routes the agent to the correct sibling once the place is known, per result type. It also handles the failure path: retry with a broader query or a place name when nothing matches.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Meridian Dispatch tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?