Skip to main content
Glama
Sign In

Meridian Dispatch

by com.meridiandispatch
OverviewDiscussionsAdmin

List festivals and events

list_events
Read-onlyIdempotent

List the festivals and events worth planning a trip around, from the Meridian Dispatch events guide. Returns each event's name, kind, where it is, the current edition's dates (a label plus ISO start and end), the best day to go, when to book, the next edition where announced, a citable URL and a citation line, sorted by start date. With no filter it returns every event; month keeps events with any day in that month; country keeps one country. Use get_place with an event's URL for its full record (schedule, where to stay, tips). For every kind of destination in a month, not just events, use get_best_time. Read-only. Dates are for one edition, so check the page before booking. An invalid month or no match returns an error message.

Input Schema

NameRequiredDescriptionDefault
monthNoAn English month name ("October", or "oct") or its number, 1 to 12 ("10"). Keeps events with any day in that month. Omit for the whole year.
regionNoOnly this part of the world. Use it for asks like "festivals in Europe"; country is more precise when the traveller names one.
countryNoKeep events in this country, by English name, e.g. "Mexico". Omit for every country.

Output Schema

NameRequiredDescriptionDefault
noteNo
eventsNoEvents, soonest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed3 schema fields changed
    • addedInput schema / properties / country / description
      Added value: +"Keep events in this country, by English name, e.g. \"Mexico\". Omit for every country."
    • changedInput schema / properties / month / description
      Previous value: -"A month name or number, e.g. \"October\" or \"10\"."New value: +"An English month name (\"October\", or \"oct\") or its number, 1 to 12 (\"10\"). Keeps events with any day in that month. Omit for the whole year."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "events": {
+      "description": "Events, soonest first.",
+      "items": {
+        "properties": {
+          "best_day": {
+            "type": "string"
+          },
+          "book": {
+            "type": "string"
+          },
+          "cite_as": {
+            "type": "string"
+          },
+          "dates": {
+            "type": "string"
+          },
+          "end": {
+            "description": "YYYY-MM-DD",
+            "type": "string"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "next_edition": {},
+          "start": {
+            "description": "YYYY-MM-DD",
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          },
+          "where": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "note": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/openWorld, so the bar is lower, yet the description adds real substance: sorting by start date, the set of returned fields, the error behavior on an invalid month or no match, and a data-currency caveat that dates are for one edition and the page should be checked before booking.

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 scope and routing, and each sentence is doing work, but the long enumeration of return fields is partly redundant given an output schema exists. Dense yet not padded; minor trimming opportunity only.

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 three-filter list tool with full schema coverage, annotations and an output schema, everything an agent needs is present: filter behavior, sibling routing, error paths, and the edition-freshness warning. Return values need not be re-explained, so nothing material is missing.

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 coverage is 100% and every parameter description already explains the filter behavior (month name or number, region scoping, country by English name). The description restates filter semantics rather than adding new syntax or format detail, so the 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?

Specific verb+resource+source: "List the festivals and events ... from the Meridian Dispatch events guide." It distinguishes itself from siblings by naming get_place (full record) and get_best_time (all destinations), so an agent can route correctly without opening a 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 when-to-use and when-not: use get_place with an event URL for the full record, and get_best_time for every kind of destination in a month. Filter semantics (no filter = everything, month = any day in that month, country = one country) are stated outright.

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