Meridian Dispatch

Get the best time to go

get_best_time

Read-onlyIdempotent

Get the best time to visit from the Meridian Dispatch guides, in one of two modes. Give destination (a country, town, trail or ski resort) for its best months, good and avoid months, closures and crowds where known, the guide's own best-time line, and the events held there. Or give month for "where to go in March": up to 40 countries, towns, trails, ski resorts and festivals the guides recommend that month, each with its reason, events first. If both are given, destination wins. For festival dates alone use list_events; for a full planning guide use get_destination. Read-only. An unknown destination, an invalid month or neither parameter returns an error message.

Input Schema

Name	Required	Description
`month`	No	An English month name ("October", or "oct") or its number, 1 to 12 ("10"). Use this or destination.
`region`	No	With month: only this part of the world ("where in Asia in February"). Ignored with destination.
`destination`	No	A country, town, trail or ski resort, by name, e.g. "Kotor" or "Niseko". Use this or month.

Output Schema

Name	Required	Description
`note`	No
`month`	No
`crowds`	No
`source`	No	How to credit this answer: show cite_as, or link url.
`closures`	No
`best_months`	No
`destination`	No
`good_months`	No
`recommended`	No	For a month: destinations recommended then.
`avoid_months`	No
`events_there`	No
`in_their_words`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 25, 2026
- addedOutput schema / properties / recommended / items / properties / best_time_line
```
Added value: +{
+  "description": "When there is no why_now: the guide's best-time line for the whole year.",
+  "type": "string"
+}
```
- addedOutput schema / properties / recommended / items / properties / region
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / recommended / items / properties / why_now / description
```
Added value: +"Why go this month, from the guide."
```

Changed1 schema field changedOct 17, 2026

addedInput schema / properties / region

Added value: +{
+  "description": "With month: only this part of the world (\"where in Asia in February\"). Ignored with destination.",
+  "enum": [
+    "Europe",
+    "Asia",
+    "Middle East",
+    "Africa",
+    "North America",
+    "Central America and the Caribbean",
+    "South America",
+    "Oceania"
+  ],
+  "type": "string"
+}

Changed1 schema field changedOct 17, 2026

addedOutput schema / properties / source / properties / corrections

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

AddedOct 6, 2026

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, and the description usefully adds unannotated behavior: precedence between parameters, that region is ignored with destination, the ~40-result ceiling for month mode, ordering (events first), and that unknown destination / invalid month / no params return an error rather than throwing. Only minor repetition of "Read-only" is wasted.

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 the two-mode framing and dense but purposeful; every clause adds routing or scope information. The long run-on enumeration of return contents is slightly heavy, but nothing here 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?

With 3 optional params, no required params, and an output schema handling return shape, the description supplies exactly the missing pieces: mode selection, precedence, exclusions, sibling alternatives, and error behavior. Nothing an agent needs to call it correctly is absent.

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, but the description adds cross-parameter semantics the schema does not encode: destination overrides month, and region applies only with month. It does not, however, add format detail for month beyond what the schema already says.

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 resource (best-time guidance from Meridian Dispatch guides) and enumerates precisely what each mode returns: best/good/avoid months, closures, crowds, the guide's best-time line, events; or up to 40 places for a month. It is immediately distinguishable from get_destination (full planning guide) and list_events (festival dates alone).

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 frames two modes with the input that selects each, resolves the ambiguous case ("If both are given, destination wins"), and routes to two named siblings with the condition that selects them. Error conditions are also stated, so an agent knows the failure envelope.

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?