Loading ToolBench
A Model Context Protocol (MCP) server for Hong Kong and cross-border open data
DragonMCP demonstrates solid fundamentals with 10 well-named tools covering transit, weather, and mapping across HK and Mainland China. All tools have descriptions (100-250 chars, within baseline range) and Zod-based schemas. Naming follows verb_noun convention consistently (search_, get_, amap_). However, several output schemas are TEXT-ONLY (no structured field documentation), error handling lacks recovery guidance, and parameter descriptions are sometimes terse. Tools like amap_transit_direction and amap_bicycling_direction could benefit from explicit return-value documentation. Overall quality is production-ready for read-only operations but would benefit from richer output schemas and error categorization.
Get bicycling directions using Amap
Get driving directions between two locations using Amap
Search for Places of Interest (POI) in Mainland China using Amap (Gaode Map)
Get public transit directions using Amap
Get walking directions between two locations using Amap
Get structured active tropical cyclone, rainstorm, and other weather warnings from the Hong Kong Observatory. Returns the tropical cyclone signal (null, 1, 3, 8NE, 8SE, 8SW, 8NW, 9, 10), the rainstorm signal (null, amber, red, black), issue and update times, and any other warnings in force.
Output schemas not documented. All tools return TEXT responses without structured field definitions. LLMs cannot parse results predictably or chain outputs to downstream calls. e.g., search_mtr_schedule returns plaintext without station IDs, line codes, or arrival times as separate fields.
No error handling guidance. Tools return plaintext summaries but lack error classification (retryable vs user-fixable vs fatal) or recovery hints. e.g., if MTR is unreachable, the error message should suggest 'Call system_run_selftest to check upstream services' instead of a generic failure.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 69 | <=2025-11-25 | v2 |
| 2026-03-09 | C | 61 | - | v1 |
Get the current weather report and active warnings from the Hong Kong Observatory
Plan an MTR journey between any two stations and get real-time arrivals for the boarding leg. Covers all 10 lines and all 98 stations, including transfers. Routes minimise the number of transfers, not travel time — no inter-station running times are available, so this does not claim to find the fastest route.
Unified transit search for Hong Kong and Mainland China. Routes HK queries to live MTR schedules and CN queries to Amap transit planning.
Run a live health check against every upstream data source (MTR, HK Observatory, Amap). Returns which sources are reachable right now.
Parameter descriptions for Amap direction tools are sparse. 'Origin longitude,latitude' and 'Destination longitude,latitude' lack format guidance (exact decimal places, accepted range -180 to 180, example: '116.481028,39.989643'). LLMs may pass invalid coordinate strings.
No pagination or result limits documented. If amap_search_poi or search_transit_route return large result sets, no indication of max items returned or how to paginate. High-volume results waste tokens and risk context exhaustion.
Tool composition gap: search_mtr_schedule and hk_typhoon_signal are independent, but weather warnings (typhoons, rainstorms) should influence transit route planning. No composite tool or guidance to chain weather checks before planning travel.