Meridian Dispatch

Get a country or town guide

get_destination

Read-onlyIdempotent

Read the Meridian Dispatch guide to one country or one town, for planning a stay there. Returns: why go, how long to stay, the best months, getting there and around, practical FAQ answers, a structured fact sheet where one exists (nights, months, travel times in minutes, areas to stay, ranked top things, day trips, watch-outs), up to 15 ranked places worth your time with their own guide links, recommended hotels, the town guides of a country, related dispatches and a citation. Use it for "what to do in X", "how many days in X" or "where to stay in X". For a single sight, trail, event or ski resort use get_place; for a long-form dispatch use get_dispatch; to find a destination by theme use search_guides; for towns within reach use list_nearby. Matching tries a country first, then a town. A country with town guides but no country guide returns its town guides and dispatches instead. Read-only. An unknown name returns an error message.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	One country or town, by English name, e.g. "Slovenia" or "Bled". Case and accents are ignored. Not a sight or region: use get_place or search_guides for those.
`country`	No	The country of the town, by English name, to tell apart towns that share a name (Granada, Valencia, Mérida). Omit when name is a country or a unique town.

Output Schema

TableJSON Schema

Name	Required	Description
`lat`	No
`lng`	No
`name`	No
`note`	No
`type`	No
`photo`	No	Lead photograph: url, alt text and credit.
`stays`	No	Hotels the guide recommends.
`places`	No	The places worth your time, ranked.
`source`	No	How to credit this answer: show cite_as, or link url.
`country`	No
`summary`	No
`overview`	No	Opening paragraphs of the guide.
`planning`	No	Short answers: days needed, best time, getting there, getting around, language, money.
`practical`	No	Practical questions and answers not already covered by planning.
`dispatches`	No	Related long-form dispatches.
`fact_sheet`	No	Structured planning data: nights, months, getting_there, where_to_stay, top_things, day_trips, watch-outs.
`best_months`	No
`coords_note`	No
`places_note`	No
`town_guides`	No	For a country: its town guides.
`places_total`	No
`country_guide`	No	meridiandispatch.com URL.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 6, 2026

changedInput schema / properties / country / description

Previous value: -"The country, to tell apart towns that share a name (Granada, Valencia, Mérida)."New value: +"The country of the town, by English name, to tell apart towns that share a name (Granada, Valencia, Mérida). Omit when name is a country or a unique town."

changedInput schema / properties / name / description

Previous value: -"A country or town name, e.g. \"Slovenia\" or \"Bled\"."New value: +"One country or town, by English name, e.g. \"Slovenia\" or \"Bled\". Case and accents are ignored. Not a sight or region: use get_place or search_guides for those."

addedInput schema / properties / name / minLength
```
Added value: +1
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "best_months": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "coords_note": {
+      "type": "string"
+    },
+    "country": {
+      "type": "string"
+    },
+    "country_guide": {
+      "description": "meridiandispatch.com URL.",
+      "type": "string"
+    },
+    "dispatches": {
+      "description": "Related long-form dispatches.",
+      "items": {
+        "properties": {
+          "country": {
+            "type": "string"
+          },
+          "last_updated": {
+            "type": "string"
+          },
+          "photo": {
+            "type": "string"
+          },
+          "summary": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "town": {
+            "type": "string"
+          },
+          "type": {
+            "enum": [
+              "dispatch",
+              "itinerary",
+              "country",
+              "town",
+              "venue",
+              "trail",
+              "event",
+              "ski_resort",
+              "museum"
+            ],
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "fact_sheet": {
+      "description": "Structured planning data: nights, months, getting_there, where_to_stay, top_things, day_trips, watch-outs.",
+      "type": "object"
+    },
+    "lat": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "lng": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "name": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "overview": {
+      "description": "Opening paragraphs of the guide.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "photo": {
+      "description": "Lead photograph: url, alt text and credit.",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "places": {
+      "description": "The places worth your time, ranked.",
+      "items": {
+        "properties": {
+          "lat": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "lng": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          },
+          "why": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "places_note": {
+      "type": "string"
+    },
+    "places_total": {
+      "type": "integer"
+    },
+    "planning": {
+      "description": "Short answers: days needed, best time, getting there, getting around, language, money.",
+      "type": "object"
+    },
+    "practical": {
+      "description": "Practical questions and answers not already covered by planning.",
+      "items": {
+        "properties": {
+          "a": {
+            "type": "string"
+          },
+          "q": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "source": {
+      "description": "How to credit this answer: show cite_as, or link url.",
+      "properties": {
+        "canonical_url": {
+          "type": "string"
+        },
+        "cite_as": {
+          "description": "A ready-made citation line: title, publisher, date and URL.",
+          "type": "string"
+        },
+        "last_updated": {
+          "type": "string"
+        },
+        "license": {
+          "type": "string"
+        },
+        "publisher": {
+          "type": "string"
+        },
+        "terms": {
+          "type": "string"
+        },
+        "title": {
+          "type": "string"
+        },
+        "url": {
+          "description": "Link for the reader (carries referral tags).",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "stays": {
+      "description": "Hotels the guide recommends.",
+      "items": {
+        "properties": {
+          "lat": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "lng": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "why": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "town_guides": {
+      "description": "For a country: its town guides.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "type": {
+      "enum": [
+        "country",
+        "town"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 2, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them by disclosing resolution order (country first, then town), the fallback when a country has town guides but no country guide, and that an unknown name returns an error message. These are non-obvious behaviors an agent needs.

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 purpose and scope, then alternatives, then edge cases. The long enumerated 'Returns:' list partially duplicates the existing output schema, which is the only real inefficiency in an otherwise tight block.

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?

Covers purpose, use cases, sibling routing, resolution behavior, fallbacks, and error handling. With an output schema present the return-value enumeration is optional, but nothing an agent needs to invoke this correctly 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, but the description adds resolution semantics that the schema does not: matching tries a country first, then a town, and the country param exists to disambiguate same-named towns. Useful, though slightly redundant with the schema's own country description.

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 (read the Meridian Dispatch guide to one country or one town) and scopes it to trip planning. An agent can distinguish it from get_place, get_dispatch, and search_guides without opening any schema.

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 concrete use cases ('what to do in X', 'how many days in X', 'where to stay in X') and explicitly routes alternatives: get_place for a single sight/trail/event/resort, get_dispatch for long-form, search_guides for theme search, list_nearby for towns within reach. When-not conditions are spelled out.

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?