Setup tool for Vietnamese Legal MCP server and AI Skill (Cursor, Claude, Codex, Windsurf, Antigravity, Gemini CLI)
Vietnamese Legal MCP has well-structured tool definitions with complete input schemas and clear descriptions. All 8 tools follow verb_noun naming (search_, find_, get_, list_). Descriptions are concise (15-60 chars) and explain purpose clearly. Input schemas use proper JSON Schema with types and enums. However, output schemas are not documented, LLMs cannot predict response structure for downstream chaining. Parameter descriptions are minimal (5-15 chars), lacking format guidance and constraints. No error handling guidance visible. Tools are read-only (good for safety) but lack idempotent/readOnly annotations. Date parameters lack format validation hints. No pagination guidance despite list_regulations and search_regulations accepting limits.
Find regulation by code
Find regulations referencing a specific code
Find related regulations
Get field of law codes
Get master codes - lookup regulation_level_id and governor_id
List regulations with various filters
Output schemas not documented. LLMs cannot predict response structure (fields, types, nested objects) for downstream tool chaining or data extraction. Breaks pattern:tool-chain and pattern:response-shaper.
Parameter descriptions are minimal (5-15 chars). Lack format guidance for dates (YYYY-MM-DD format stated in description but not in schema pattern), enums (regulation_status_type values clear but no guidance on when to use each), and numeric bounds (top_k, limit, regulation_level_id have no min/max stated). Violates pattern:constrained-input and pattern:tool-description.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | 2026-07-28+ | v2 |
Search regulation chunks by vector with Vietnamese legal keywords
Search regulations by Vietnamese title
No error handling guidance. Tool descriptions do not explain what to do if a regulation_code is not found, if API rate limits are hit, or if date ranges are invalid. Violates pattern:recovery-guide.
No tool annotations (readOnlyHint, idempotentHint). All tools are read-only and idempotent, but LLMs cannot infer this without explicit annotations. Violates current MCP spec (2026-07-28) tool annotation pattern.
Pagination not explicitly documented. list_regulations and search_regulations accept 'limit' but no 'offset', 'page', or 'next_cursor' parameters visible. No guidance on total count or whether results are truncated. Violates pattern:paginated-result.