MCP Server: 台灣不動產實價登錄資料 (Taiwan Real Estate Transaction Registry Data)
Server has 5 well-named tools with consistent verb_noun patterns (search_*, get_*). All tools have descriptions (avg 80 chars, within baseline 34-392). Input schemas are present and use Zod validation with descriptions. However, output schemas are completely undocumented, LLMs cannot predict response structure. Parameter descriptions lack format constraints (e.g., 'YYYYMM' format stated but not enforced as regex). No enum constraints for property_type or period values. Error handling is minimal, no recovery guidance or actionable error messages. No tool annotations (readOnlyHint present in metadata but not declared in schema). Missing pagination documentation despite tools accepting 'limit' parameters.
取得區域房價統計:均價、中位數、最高最低、交易量
分析區域房價趨勢,提供月度或季度平均價與漲跌幅
取得最新一期不動產成交案件,依日期排序
依行政區查詢新北市不動產實價登錄成交案件
依日期範圍查詢不動產成交案件,可加價格篩選
Output schemas completely undocumented. LLMs cannot predict response structure, field names, or types. Tools return ToolResult with 'content' and 'isError' but actual data shape is invisible.
Parameter 'property_type' accepts free-form strings ('住家', '商辦', '其他') but no enum constraint. LLMs will hallucinate invalid values. Same issue with 'period' (monthly vs quarterly).
Date format 'YYYYMM' stated in description but not enforced via regex pattern in schema. LLMs frequently misformat dates (e.g., '2025-01' instead of '202501').
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 61 | 2026-07-28+ | v2 |
No error handling guidance. Tools return isError flag but no recovery hints. If start_date is invalid or district not found, LLM receives no actionable next step.
Pagination parameters (limit) present but no documentation of total count, next_cursor, or result limits. Tools accept limit up to 100 but no guidance on default behavior or max safe values.