Deutsche Gesetze MCP demonstrates solid tool design with clear naming conventions (all tools start with action verbs: list_, get_, search_), comprehensive descriptions (avg 180 chars, within 10-1024 baseline), and well-structured input schemas with type definitions and parameter descriptions. All 6 tools have explicit descriptions and typed parameters. However, output schemas are not documented in the source code, the tool definitions show input schemas but no explicit return type documentation. Error handling is present (ToolError raised for missing paragraphs) but lacks recovery guidance. No tool annotations (readOnlyHint, destructiveHint) despite all tools being read-only. Parameter descriptions are good but could be more prescriptive about format constraints (e.g., exact enbez format with § symbol).

• Add explicit output schema documentation to all tools. Document return types as JSON Schema (e.g., list_laws returns array of {jurabk: string, full_title: string, norm_count: integer}). This enables LLMs to plan multi-step operations.
• Add readOnlyHint: true annotation to all 6 tools in FastMCP tool registration. This signals to clients that these tools are safe to cache and retry without side effects.
• Enhance error handling in get_paragraphs_range and search_laws to include recovery suggestions. E.g., 'No results found. Try: (1) verify law abbreviation with list_laws, (2) check exact paragraph format with get_law_structure, (3) broaden search query.'
• Add regex pattern constraints to enbez parameters. Define pattern like '^(§|Art)\.? \d+' in schema to enforce format validation at the protocol level, not just in description text.
• Document pagination behavior explicitly. list_laws and search_laws support limit/offset; clarify max result counts (200 for list_laws, 100 for search_laws) and whether total_count is returned for planning multi-page queries.

Inferred effective spec: 2026-07-28+.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry