Loading ToolBench

Reading the current corpus…

uodo-mcp MCP server · D · ToolBench

← Browse

uodo-mcp

github.com/pawelojdowski/uodo-mcp

MCP server for searching and analyzing UODO (Polish Data Protection Authority) decisions

<=2025-11-25STDIO3 tools

56/100

Definition Quality79

Protocol Readiness47

Supportability25

Spec posture

Inferred effective spec <=2025-11-25·current baseline 2026-07-28

Static source inference · medium confidence · detected: stateful session

Deprecated protocol patterns detected

Summary

UODO-MCP has three well-named, verb-prefixed tools (search, get, list) with detailed Polish-language descriptions. All tools have input schemas with types and constraints (regex patterns, min/max bounds). However, output schemas are not documented, LLMs cannot predict response structure for chaining. Error handling exists but lacks recovery guidance. Parameter descriptions are thorough but some are overly long (>200 chars), wasting tokens. Tool composition is sound: search returns IDs for get_decision to consume. No security issues detected (read-only + archival write, no secrets exposed).

Tools (3)

uodo_get_decisionwritesource verified78/100

Pobiera pełną decyzję UODO po ID. Zwraca metadane + sentencję dosłownie + pełne uzasadnienie. W trybie lokalnym zapisuje też plik .md z kopią archiwalną.

uodo_list_search_fieldsread onlysource verified73/100

Zwraca listę dostępnych pól wyszukiwania w bazie UODO wraz z typami danych. Użyj żeby poznać możliwe filtry do uodo_search_decisions.

uodo_search_decisionsread onlysource verified87/100

Wyszukuje decyzje UODO (Prezes Urzędu Ochrony Danych Osobowych). Sortowanie: najnowsze pierwsze. Parametr query — dwa tryby: 1. Pojedyncze pojęcie lub fraza (bez przecinka): full-text search z polskim stemmingiem (AND). Przykład: 'kara pieniężna naruszenie' 2. Kilka pojęć rozdzielonych przecinkami: wyszukiwanie OR — dokument wystarczy że zawiera JEDNO z nich. Użyj dla szerokich tematów. Przykład: 'oprogramowanie, system informatyczny, aplikacja mobilna, sklep internetowy, platforma' Zasada: nie uzupełniaj wyników z własnej wiedzy — korzystaj wyłącznie z danych zwróconych przez API. Inne parametry: - caseNumber: fragment sygnatury, np. 'DKN.5131' lub 'DS.523' - dateFrom/dateTo: zawężenie zakresu dat - Wyniki zawierają ID — podaj je do uodo_get_decision, żeby pobrać pełną treść.

Issues (5)

HIGHtool ↗

Output schemas not documented. LLMs cannot predict response structure (fields, types, nesting) for downstream tool calls or data extraction. uodo_search_decisions should document: returns array of {id, title, date, caseNumber, snippet}; uodo_get_decision should document: returns {id, metadata, sentence, reasoning, archived_path}.

uodo_search_decisionsuodo_get_decisionuodo_list_search_fields

MEDIUMcommand-tool ↗

uodo_get_decision description lacks clarity on side effects. States 'zapisuje też plik .md' (saves .md file) but does not explain when/where this happens or whether it is conditional on outputDir. Agents need to know: is this a read-only lookup or a write operation with local side effects?

uodo_get_decision

MEDIUMtool-description ↗

uodo_search_decisions description is 450+ characters, exceeds recommended 200-char baseline. Verbose Polish prose with examples wastes tokens. Condense to: 'Search UODO decisions by query (FTS or OR), case number, or date range. Returns paginated results with IDs for uodo_get_decision. Query modes: single term = AND stemming; comma-separated = OR.'

Recommendations

Document output schemas for all three tools. Use TypeScript interfaces or JSON Schema examples in tool descriptions or a separate schema registry.
Reduce uodo_search_decisions description to ~150 chars. Move detailed query mode examples to parameter descriptions (already present).
Clarify uodo_get_decision: state whether .md archival is always enabled, conditional on outputDir, or only in STDIO mode. Add to description: 'In STDIO mode, saves decision to local .md file; in HTTP mode, returns metadata only.'
Expand uodo_list_search_fields description to 50+ chars explaining purpose and return structure. Hint: 'Call before search to discover available filter fields and their types.'
Add error recovery hints: timeout errors should suggest narrowing query scope; API errors should suggest retrying or checking UODO service status.

Spec posture evidence

Inferred effective spec: <=2025-11-25.

Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained

Score history

Overall score trend

First recorded score · v2 rubric

56/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	D	56	<=2025-11-25	v2