Loading ToolBench
Hong Kong environment MCP Server providing environment data tools
Server has only 1 tool with significant quality gaps. Tool naming is acceptable (verb_noun pattern: get_current_aqhi), but the input schema is completely empty (no parameters defined), which triggers a hard cap per the rubric. Tool description is present and reasonably detailed (204 chars, within baseline 10-1024 range), but the empty schema and lack of output documentation are critical failures. The tool is properly registered with FastMCP, but parameter descriptions cannot be evaluated since no parameters exist. No error handling guidance is visible in the tool definition.
Current Air Quality Health Index (AQHI) at individual general and roadside Air Quality Monitoring stations in Hong Kong. The AQHIs are reported on a scale of 1 to 10 and 10+ and are grouped into five AQHI health risk categories with health advice provided.
No input schema defined. Tool 'get_current_aqhi' has empty input parameters ({}), cannot validate expected inputs or guide LLM on what parameters are accepted.
No output schema documented. The tool returns List[Dict] but provides no field-level schema describing what keys and types are in each dictionary (station, aqhi_value, risk_level, station_type). LLMs cannot plan downstream operations without knowing response structure.
No error handling guidance. The _get_current_aqhi() function can return an error dict (if fetch_xml_from_url fails), but the tool definition provides no recovery hints or error classification for the LLM (retryable vs fatal). LLM will not know what to do if the call fails.
No parameter descriptions. Although the tool accepts no parameters currently, the description does not explain what data is returned, when to call it, or how to interpret AQHI values (scale 1-10+, health risk categories). Users/LLMs must infer context from the title alone.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 14 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 23 | - | v1 |
No rate limiting or timeout documented. The tool makes an external HTTP call to HK government API (aqhi.gov.hk) but provides no visibility into timeouts, retry behavior, or rate limits. Agents could hang or overload the external service.