Meridian Dispatch

List the World's Best places

list_best_places

Read-onlyIdempotent

List Meridian Dispatch's ranked World's Best places: the 20 best in the world or the 10 best in one country, overall or within one category. Use it for "top things to do in X" or "best beaches in X". For one town's highlights use get_destination; for places near a point use list_nearby; for any other search use search_guides. Returns the list's title, the places in rank order (rank, name, where, a one-line summary, the place's own guide URL where one exists, and a coordinate), the other categories available for that scope, and a citation. Read-only. A country or category with no list returns an error that names the ones that exist.

Input Schema

Name	Required	Description	Default
`country`	No	The country to rank, by English name, e.g. "Italy". Omit for the world list.
`category`	No	One kind of place: landmarks, museums, towns, wilderness, hiking trails, scenic drives, parks, viewpoints, beaches, shopping, wildlife, wellness or ski resorts. Singular and plural both work. Omit for the overall list.

Output Schema

Name	Required	Description
`list`	No
`ranked`	No	Best first.
`source`	No	How to credit this answer: show cite_as, or link url.
`other_categories`	No

Schema Changelog

Changes observed during successful MCP inspections.

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.5/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 non-open-world behavior. The description adds genuinely useful behavioral context beyond them: the error semantics for an empty country/category (an error naming the existing lists) and confirmation of the scoped return contents. It stops short of rich detail but the annotation bar is already met.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, all front-loaded: purpose/scope first, then usage triggers and alternatives, then return shape, then error behavior. No filler and no redundancy with the 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?

With zero required params, a rich output schema, and full annotation coverage, the description supplies exactly the missing pieces: when to choose this tool, the alternates to avoid, and what happens on an empty result. An agent has everything needed to invoke it correctly.

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%, so both parameters are fully documented in the schema with examples and omission semantics. The description reinforces intended usage through sample phrases but adds no format, syntax, or constraint detail beyond what the schema provides, which is the expected baseline case.

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 (list) and a well-defined resource (Meridian Dispatch's ranked World's Best places), including scope dimensions (20 world / 10 country, overall or category). It explicitly distinguishes itself from get_destination, list_nearby, and search_guides, so an agent can route without opening sibling 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?

Gives concrete trigger phrases ('top things to do in X', 'best beaches in X') plus explicit when-not conditions routing to three named alternatives for town highlights, proximity, and other searches. 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 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?