MCP server that gives Claude Code access to the DSO regulation database. Provides semantic search over EU legislative acts and regulatory documents related to DSO (Distribution System Operator) operations, gas/hydrogen integration, and energy regulation.
MAMA provides 4 read-only regulatory search tools with complete JSON schemas and reasonable descriptions. Tool names follow verb_noun convention (search_, get_, list_). Schemas include proper types and constraints (e.g., top_k with default and max). However, descriptions lack LLM-optimization guidance (e.g., 'when to use this vs get_article'), parameter descriptions are minimal (e.g., 'Filter by chunk type' lacks enum values), and error handling is absent from visible code. Output schemas are documented in code but not in tool registration metadata. No tool annotations (readOnlyHint, idempotentHint) despite all being read-only. Missing guidance on multi-step workflows (e.g., 'search first, then get_article for full text').
Return the full metadata record for one act.
Get a specific article by CELEX number and article number.
Enumerate acts in the database with optional filters.
Search the EU DSO Entity regulatory document database. Contains article-level chunks from EU legislation and paragraph-level chunks from reports and publications. Key acts: 2024/1789 (Gas Market Regulation), 2024/1788 (Gas Directive), 2019/943 (Electricity Regulation), 2019/944 (Electricity Directive), 2024/1366 (NC Cybersecurity), 2024/1106 (REMIT amendment), 2025/2359 (low-carbon fuels), 2023/1184 & 2023/1185 (RFNBO). Each article chunk includes structural_path, provision_role, and act_type. Use this for semantic search. For exact article lookup, use get_article.
Parameter descriptions lack actionable constraints. 'Filter by chunk_type' does not enumerate valid values (article, recital, definition, etc.). LLMs cannot infer enums from prose.
Tool descriptions do not explain when to use each tool or how they compose. 'Get a specific article' vs 'Search the database', when should an LLM pick one over the other? No guidance on multi-step workflows.
No error handling visible in tool definitions. What happens if CELEX is invalid? If article_number does not exist? LLMs need recovery guidance, not silent failures or exceptions.
No tool annotations despite all tools being read-only. Adding readOnlyHint=true to all 4 tools signals safety to agents and enables optimizations (e.g., caching, parallel execution).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 53 | 2026-07-28+ | v2 |
Output schemas documented in Python code but not exposed in MCP tool registration. LLMs cannot see what fields search_regulations returns without reading implementation.