Meridian Dispatch

Get a venue, trail, event or ski resort

get_place

Read-onlyIdempotent

Read the Meridian Dispatch field record for one place: a sight, museum, beach or park, a trail or scenic drive, an event, or a ski resort. Returns the best time to go, how long it takes, effort, season, access, how to get there and what goes wrong, plus the best months, practical answers, a photo, the town guide link, reviews by travellers who went when there are any (traveller_reviews) and a citation; an event adds its dates and schedule, a trail its route facts. Use it once you know the place. For a whole country or town use get_destination; for a dispatch use get_dispatch; to find a place you cannot name exactly use search_guides; for what else is close use list_nearby. Give url, or name (at least one). A place mentioned on a town guide with no page of its own returns its short write-up and that guide. A URL of a town, country or dispatch page returns that guide instead. Read-only. No match returns an error message.

Input Schema

Name	Required	Description
`url`	No	The place's meridiandispatch.com page URL, from a search_guides or get_destination result. Takes priority over name.
`name`	No	The place's name, e.g. "Kotor Old Town" or "Grunas Waterfall". Exact names match first, then names that contain it.
`town`	No	The town the place is in or visited from, e.g. "Kotor", to narrow a name shared by several places.
`country`	No	The place's country, by English name, to narrow a name shared by several places.

Output Schema

Name	Required	Description
`lat`	No
`lng`	No
`why`	No
`name`	No
`town`	No
`type`	No
`event`	No	For an event: dates, best day, when to book, where to stay, schedule.
`photo`	No	Lead photograph: url, alt text and credit.
`source`	No	How to credit this answer: show cite_as, or link url.
`country`	No
`summary`	No
`overview`	No
`practical`	No	Questions travellers ask about the place, each {q, a}, as the page answers them. Where the page can open at its FAQ, each also has a url: cite that link when the answer came from it.
`town_guide`	No	meridiandispatch.com URL.
`at_a_glance`	No	Best time, time needed, effort, season, access.
`best_months`	No
`official_tickets`	No	The place's own online ticket shop, when it has one. Never a reseller.
`traveller_reviews`	No	Reviews by travellers who went, when there are any: verdict (Worth it to Skip it), rating out of 5, count, and up to five reviews, each {verdict, text, by, visited, countries_visited, published}. Opinions, not the guide.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

addedOutput schema / properties / traveller_reviews

Added value: +{
+  "description": "Reviews by travellers who went, when there are any: verdict (Worth it to Skip it), rating out of 5, count, and up to five reviews, each {verdict, text, by, visited, countries_visited, published}. Opinions, not the guide.",
+  "type": "object"
+}

Changed1 schema field changedOct 17, 2026

changedOutput schema / properties / practical / description

Previous value: -"Questions travellers ask about the place, each {q, a}, as the page answers them."New value: +"Questions travellers ask about the place, each {q, a}, as the page answers them. Where the page can open at its FAQ, each also has a url: cite that link when the answer came from it."

Changed3 schema fields changedOct 17, 2026

addedOutput schema / properties / official_tickets

Added value: +{
+  "description": "The place's own online ticket shop, when it has one. Never a reseller.",
+  "type": "string"
+}

addedOutput schema / properties / practical / description

Added value: +"Questions travellers ask about the place, each {q, a}, as the page answers them."

addedOutput schema / properties / source / properties / corrections

Added value: +{
+  "description": "How to report an error on this page (suggest_edit).",
+  "type": "string"
+}

Changed5 schema fields changedOct 6, 2026

addedInput schema / properties / country / description

Added value: +"The place's country, by English name, to narrow a name shared by several places."

changedInput schema / properties / name / description

Previous value: -"The place name, e.g. \"Kotor Old Town\" or \"Grunas Waterfall\"."New value: +"The place's name, e.g. \"Kotor Old Town\" or \"Grunas Waterfall\". Exact names match first, then names that contain it."

addedInput schema / properties / town / description

Added value: +"The town the place is in or visited from, e.g. \"Kotor\", to narrow a name shared by several places."

changedInput schema / properties / url / description

Previous value: -"A meridiandispatch.com page URL."New value: +"The place's meridiandispatch.com page URL, from a search_guides or get_destination result. Takes priority over name."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "at_a_glance": {
+      "description": "Best time, time needed, effort, season, access.",
+      "type": "object"
+    },
+    "best_months": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "country": {
+      "type": "string"
+    },
+    "event": {
+      "description": "For an event: dates, best day, when to book, where to stay, schedule.",
+      "type": "object"
+    },
+    "lat": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "lng": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "name": {
+      "type": "string"
+    },
+    "overview": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "photo": {
+      "description": "Lead photograph: url, alt text and credit.",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "practical": {
+      "items": {
+        "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"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "town": {
+      "type": "string"
+    },
+    "town_guide": {
+      "description": "meridiandispatch.com URL.",
+      "type": "string"
+    },
+    "type": {
+      "type": "string"
+    },
+    "why": {
+      "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 adds genuinely non-obvious behavior: a place without its own page returns a short write-up plus its parent guide, a URL belonging to a town/country/dispatch returns that guide instead, and no match returns an error. These fallback semantics materially change how an agent should interpret the result and are not derivable from annotations or schema.

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 routing alternatives are front-loaded and the edge cases are worth their space, but the return-value enumeration ('how to get there and what goes wrong, plus the best months, practical answers, a photo...') is a dense run-on list that partly duplicates what the output schema already conveys.

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?

Given an output schema exists, the description need not explain returns, yet it covers identification inputs, disambiguation inputs, fallback behavior and error behavior. An agent has everything needed to call this correctly or route elsewhere.

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; the description adds a real constraint not encoded in the schema — 'Give url, or name (at least one)' — since zero parameters are marked required. It adds less about town/country narrowing, which the schema already explains.

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 field record for one place') and enumerates the entity types covered (sight, museum, beach, park, trail, scenic drive, event, ski resort). An agent can distinguish this from get_destination, 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?

Explicit trigger ('Use it once you know the place') plus four named alternatives with the condition that selects each: get_destination for country/town, get_dispatch for a dispatch, search_guides when the name is imprecise, list_nearby for proximity. Nothing is left to inference.

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?