mcp-nsa
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Przeszukuje Centralna Baze Orzeczen Sadow Administracyjnych (CBOSA) - Naczelny Sad Administracyjny + 16 wojewodzkich sadow administracyjnych. TU zyje merytoryczne orzecznictwo RODO/UODO, podatkowe, celne, kontrola decyzji administracji publicznej. SAOS NIE indeksuje tego pionu. Dla MVP zwraca top-N wynikow z pelnymi metadanymi (sygnatura, sad, data, sklad, hasla tematyczne, podst. prawna, fragment tresci). Max 5 dokumentow pobranych w jednym zapytaniu - kazda kolejna szczegolowa lektura przez get_judgment z konkretnym doc_id. |
| get_judgmentA | Pobiera pelne orzeczenie z CBOSA po jego doc_id (10-znakowy hex). Zwraca metadane (sygnatura, sad, data, sklad, hasla tematyczne, podstawe prawna, typ orzeczenia) + pierwsze 2000 znakow tresci (sentencja + uzasadnienie). doc_id pochodzi z wynikow narzedzia 'search'. |
| search_by_caseA | Skrot: szuka orzeczenia po sygnaturze. Odpowiednik search z parametrem caseNumber. Jesli orzeczenie nie znajdzie sie - sygnatura moze byc z sadu powszechnego/SN/TK/KIO (uzyj wtedy saos__search_by_case). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Tools are mostly distinct: search for general queries, search_by_case for case number lookup, and get_judgment for full retrieval by ID. The only minor overlap is that search_by_case is described as a shortcut for search with a case number, which could cause slight confusion but is clearly documented.
All tool names use a consistent snake_case pattern with verbs (get, search) followed by nouns or qualifiers. The naming is uniform and predictable across the set.
With 3 tools covering search, retrieval, and case-specific lookup, the set is minimal but reasonable for a focused legal database. The scope is narrow (administrative courts), so no heavy tool count is needed.
The tools cover basic search and retrieval, but notable gaps exist: lack of filtering by date, court level, or other metadata in search, and get_judgment only returns the first 2000 characters, limiting full-text access. Agents may need workarounds for deeper queries.