Skip to main content
Glama

Meridian Dispatch

by com.meridiandispatch
OverviewDiscussionsAdmin

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 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

TableJSON Schema
NameRequiredDescriptionDefault
urlNoThe place's meridiandispatch.com page URL, from a search_guides or get_destination result. Takes priority over name.
nameNoThe place's name, e.g. "Kotor Old Town" or "Grunas Waterfall". Exact names match first, then names that contain it.
townNoThe town the place is in or visited from, e.g. "Kotor", to narrow a name shared by several places.
countryNoThe place's country, by English name, to narrow a name shared by several places.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNo
lngNo
whyNo
nameNo
townNo
typeNo
eventNoFor an event: dates, best day, when to book, where to stay, schedule.
photoNoLead photograph: url, alt text and credit.
sourceNoHow to credit this answer: show cite_as, or link url.
countryNo
summaryNo
overviewNo
practicalNo
town_guideNomeridiandispatch.com URL.
at_a_glanceNoBest time, time needed, effort, season, access.
best_monthsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/no-destructive, but the description adds real edge-case behavior unavailable elsewhere: a place with no page returns its short write-up plus its town guide, a town/country/dispatch URL returns that guide instead, and no match returns an error message rather than an empty result.

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 routing, but the second sentence is a long, comma-heavy inventory of return fields that is hard to parse in one pass. Every element is relevant, yet the returns list could be tightened or deferred to the output schema.

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 4-parameter, zero-required lookup tool with an output schema, the description covers purpose, routing, input requirement and fallback behavior completely. Nothing an agent needs in order to call it 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 baseline is 3, but the description adds a genuine constraint the schema does not enforce: at least one of url or name is required despite zero required properties. The town/country narrowing purpose is already in the schema.

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?

Specific verb+resource: 'Read the Meridian Dispatch field record for one place', with the resource scope enumerated (sight, museum, beach, park, trail, event, ski resort). It also names the siblings it is not (get_destination, get_dispatch, search_guides, list_nearby), so an agent can route 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 (whole country/town, dispatch, unknown name, nearby). Also states the input precondition: 'Give url, or name (at least one).'

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

All Meridian Dispatch toolsInspect
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