Skip to main content
Glama

Meridian Dispatch

by com.meridiandispatch
OverviewDiscussionsAdmin

Get a dispatch or itinerary

get_dispatch
Read-onlyIdempotent

Read one Meridian Dispatch long-form dispatch or multi-day itinerary. A dispatch is a reported piece on one place: returns its headline, standfirst, opening excerpt, themes, publish date, photo and links to its town and country guides (the full text stays on the page). An itinerary is a country route over several days: returns the bases in order, nights in each, where to stay and every day's activities by part of the day, each linked to its guide. Use it only for these two kinds of page. For a country or town guide use get_destination; for one sight, trail, event or ski resort use get_place; to list dispatches on a theme use search_guides with type "dispatch" or "itinerary". Lookup order: an exact URL, then an exact slug, then the single best keyword match, so a place name returns the one most relevant dispatch. Read-only. No match returns an error message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesA dispatch or itinerary URL, its slug (e.g. "hallstatt", "montenegro-beach-six-days"), or the place it covers (e.g. "Hallstatt").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNo
lngNo
noteNo
typeNo
photoNoLead photograph: url, alt text and credit.
placeNo
routeNoFor an itinerary: bases, nights and day_by_day activities.
sourceNoHow to credit this answer: show cite_as, or link url.
themesNo
excerptNo
headlineNo
publishedNo
standfirstNo
town_guideNomeridiandispatch.com URL.
country_guideNomeridiandispatch.com URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"A dispatch URL or slug (e.g. \"hallstatt\"), or the place it covers."New value: +"A dispatch or itinerary URL, its slug (e.g. \"hallstatt\", \"montenegro-beach-six-days\"), or the place it covers (e.g. \"Hallstatt\")."
    • addedInput schema / properties / query / minLength
      Added value: +1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "country_guide": {
+      "description": "meridiandispatch.com URL.",
+      "type": "string"
+    },
+    "excerpt": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "headline": {
+      "type": "string"
+    },
+    "lat": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "lng": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "note": {
+      "type": "string"
+    },
+    "photo": {
+      "description": "Lead photograph: url, alt text and credit.",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "place": {
+      "type": "string"
+    },
+    "published": {
+      "type": "string"
+    },
+    "route": {
+      "description": "For an itinerary: bases, nights and day_by_day activities.",
+      "type": "object"
+    },
+    "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"
+    },
+    "standfirst": {
+      "type": "string"
+    },
+    "themes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "town_guide": {
+      "description": "meridiandispatch.com URL.",
+      "type": "string"
+    },
+    "type": {
+      "enum": [
+        "dispatch",
+        "itinerary"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description nonetheless adds genuine behavior: the lookup precedence (URL, then slug, then best keyword match), the fact that full text stays on the page and only excerpts/links are returned, and that a no-match yields an error. It does repeat 'Read-only' from the annotations, which is the only wasted clause.

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 what the tool reads, then the two page types, then routing rules, then lookup order. Dense but every sentence carries routing or behavioral information; only the redundant 'Read-only' clause is 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?

Given one parameter, full schema coverage, an output schema, and rich annotations, the description covers purpose, page-type semantics, sibling routing, resolution order, and failure mode. 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 description coverage is 100%, so the baseline is 3, but the description adds interpretation rules the schema does not: the query is resolved as URL first, then slug, then single best keyword match, so a bare place name maps to one most-relevant dispatch. That meaningfully clarifies the single parameter beyond its schema text.

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 (read one) plus two precisely defined resources (dispatch, itinerary), and explicitly defines what each kind of page contains. It distinguishes itself from every relevant sibling by name, 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?

Explicitly scopes usage ('Use it only for these two kinds of page') and names the alternatives with their selecting conditions: get_destination for country/town guides, get_place for sights/trails/events/resorts, search_guides with type 'dispatch'/'itinerary' for listing. 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 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