Skip to main content
Glama

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

TableJSON 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.
countryNoKeep events in this country, by English name, e.g. "Mexico". Omit for every country.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
eventsNoEvents, soonest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  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 status, but the description adds real behavior: results sorted by start date, invalid month or no match returns an error message, and dates reflect a single edition so the page should be checked before booking. Error and data-freshness caveats go well beyond the structured hints.

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 alternatives before the caveats, and mostly tight. The long enumeration of returned fields (name, kind, dates, best day, booking, URL, citation) duplicates the existing output schema rather than earning its place.

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?

With an output schema present and rich annotations, the description needs only usage and caveats, and it supplies both: routing to siblings, error behavior, and the "one edition only" warning. Nothing an agent needs to call 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 schema already documents both params; the description restates the filter semantics (month keeps any day in that month, country keeps one country) but adds the combined/omission behavior ("With no filter it returns every event"). That is a modest but real addition over the schema baseline of 3.

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 ("List") plus resource ("festivals and events") and named source ("Meridian Dispatch events guide"). It draws a clear boundary against siblings get_place and get_best_time, so an agent can select it without opening schemas.

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 routing: "Use get_place with an event's URL for its full record" and "For every kind of destination in a month, not just events, use get_best_time." Filter behavior when filters are omitted is also stated (no filter = every event).

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