Loading ToolBench
Detourmap MCP server — 70,343 notable places worldwide as read-only MCP tools. Remote endpoint: https://detourmap.com/mcp
Detourmap MCP demonstrates solid tool design with clear naming, comprehensive descriptions, and well-structured schemas. All 5 tools follow verb_noun patterns (search_places, get_place, nearby_places, list_kinds, stats). Descriptions are detailed (100-250 chars) and explain WHAT, WHEN, and HOW. Input schemas are complete with proper types, constraints (min/max, enums), and parameter descriptions. Output schemas are documented in code. However, error handling lacks recovery guidance, and no tool annotations (readOnlyHint) are present despite all tools being read-only. Parameter descriptions could be more concise for LLM parsing.
Fetch one place's full record by slug (preferred, e.g. "neuschwanstein-castle") or exact name: coordinates, founding year, worldwide fame rank and tier, short description, photo URL, Wikipedia and Wikidata links, and a deep link that opens it on the map. Unsure of the slug? Call search_places first.
List all 17 place kinds (categories) with their labels and slugs. Use the key or slug in search_places and nearby_places to filter by type.
Find notable places within a radius of a given location (latitude, longitude, and distance in km). Results are sorted by distance, nearest first. Optionally filter by kind. Useful for travel planning: "What's worth visiting near me?"
Search 70,520 notable places worldwide by name (accent- and case-insensitive substring match): ruins, beaches, caves, waterfalls, volcanoes, castles, museums, ghost towns and more. Optionally filter by country (name or ISO code) and kind. Results come best-match-first, then by fame; each carries coordinates, fame rank/tier and links to the map and Wikipedia. If nothing matches, retry with a shorter fragment.
Get dataset statistics: total places, countries covered, and protocol version.
No tool annotations (readOnlyHint, idempotentHint) despite all tools being read-only and safe to retry. Agents cannot infer safety properties without explicit hints.
Error handling lacks recovery guidance. No documented error cases, retryability classification, or actionable error messages. E.g., what happens if 'place' slug is not found in get_place?
Output schemas not formally documented in tool definitions. Code shows briefOf() and fullOf() helper functions, but tool registration does not include explicit 'outputSchema' declarations.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 67 | 2026-07-28+ | v2 |
Parameter descriptions in 'kind' field are verbose (KIND_ENUM_DESC concatenates all 17 kinds inline). Should use enum constraint with brief description instead.
stats tool has empty input schema (no properties) but lacks description explaining what statistics are returned or when to call it.