Official-source temporal regulatory knowledge MCP for Korean fire inspection
Korean Fire Inspection MCP has 5 tools with clear naming (verb_noun pattern: search_, get_, trace_, list_) and domain-specific descriptions in Korean. However, critical gaps undermine production readiness: (1) Input schemas are inferred from function signatures, not explicitly visible in tool registration code, cannot verify JSON Schema structure, type constraints, or enum declarations. (2) Parameter descriptions exist in docstrings but are not formally attached to schema definitions, LLMs cannot parse them from JSON Schema. (3) Output schemas are completely undocumented, no field definitions, types, or pagination guidance. (4) No error handling guidance, tools return dicts with no recovery hints. (5) No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite all tools being read-only. Baseline: 194 chars avg description length; these average ~120 chars (below baseline). All 5 tools are read-only, reducing risk, but lack of formal schema documentation and output structure guidance prevents confident LLM integration.
공식 법령/행정규칙 ID와 기준일에 해당하는 승인 시행본 전체를 조회한다.
현재 데이터베이스 문서·조문 수와 마지막 공식 API 동기화 상태를 조회한다.
최근 동기화 오류와 담당자 검토가 필요한 변경 후보 상태를 반환한다.
기준일 현재 승인된 소방·건축 법령과 NFPC/NFTC·형식승인 기준의 원문 조항을 검색한다. source_type은 law 또는 admrul이다. 결과는 법적 결론이 아닌 공식 근거 후보다.
해당 공식 문서에서 단서·제외·경과조치 등 예외 후보를 찾아 추가 확인 사실과 함께 반환한다.
Input schemas not explicitly visible in tool registration. Function signatures show parameters (query, as_of, source_type, limit) but no JSON Schema with type constraints, enums, or min/max bounds. Cannot verify LLM can parse valid value ranges.
Output schemas completely undocumented. Tools return dicts but no field definitions, types, or structure guidance. LLMs cannot plan downstream calls or extract required IDs (e.g., official_id for chaining).
No error handling guidance. Tools return dicts with no recovery hints. If search_current_rules returns empty results or API fails, LLM has no guidance on what to try next (e.g., 'Try broader query' or 'Check as_of date').
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 44 | 2026-07-28+ | v2 |
Parameter descriptions in docstrings, not in schema. FastMCP may not expose Korean descriptions to LLM context if schema is auto-generated from function signature. Verify parameter descriptions are included in JSON Schema 'description' fields.
No tool annotations despite all tools being read-only. Missing readOnlyHint would help agents understand these tools are safe to call without side effects. Adds clarity for agent planning.