sk-registers-mcp
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 | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hladaj_subjektA | Hľadá právnické osoby v RPO (Register právnických osôb) podľa názvu, IČO alebo obce. Aspoň jeden z parametrov nazov/ico musí byť zadaný. RPO agreguje dáta z ~70 zdrojových registrov (ORSR, ZRSR, a ďalšie). |
| detail_subjektuA | Vráti kompletný detail právnickej osoby z RPO podľa IČO. Obsahuje štatutárov, spoločníkov, predmety činnosti, právnu formu a adresu. Ak historia=True, vráti aj historické záznamy (bývalí konatelia, staré adresy atď.). |
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 2 tools
The two tools have clearly distinct purposes: 'detail_subjektu' retrieves detailed information for a specific legal entity by IČO, while 'hladaj_subjekt' searches for entities across multiple criteria. There is no overlap in functionality that would cause confusion.
Both tool names follow a consistent Slovak verb_noun pattern ('detail_subjektu' and 'hladaj_subjekt'), using underscores and descriptive action-object naming. The naming is uniform and predictable across the set.
With only 2 tools, the server feels minimal for a legal entity registry domain. While it covers basic lookup and search, typical CRUD operations or additional registry functions might be expected, making it borderline thin for the apparent scope.
The tools provide search and detail retrieval, covering core lookup needs, but there are notable gaps such as update, delete, or creation operations for legal entities. The surface is functional but incomplete for full lifecycle management in a registry context.