mcp-krs
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 |
|---|---|
| get_entityA | Pobiera ODPIS AKTUALNY z Krajowego Rejestru Sadowego po numerze KRS. Zwraca pelne dane podmiotu: nazwa, forma prawna, NIP, REGON, adres, kapital zakladowy, reprezentacja (zarzad + sposob reprezentacji), prokurenci, glowny PKD, status (aktywny/likwidacja/upadlosc) + URL do wyszukiwarki KRS. Numer KRS uzupelnij zerami wiodacymi (lub podaj krotszy - zostanie wyrównany do 10 cyfr). |
| get_entity_fullA | Pobiera ODPIS PELNY z KRS (z historia wpisow - kazda zmiana, kazde wykreslenie, wszystkie poprzednie sklady zarzadu). Wieksza odpowiedz, uzywaj kiedy potrzebujesz historii zmian, nie tylko stanu aktualnego. |
| get_boardA | SKROCONA wersja: tylko sklad zarzadu + sposob reprezentacji + prokurenci. Szybciej niz get_entity gdy potrzebujesz tylko 'kto reprezentuje X'. Bazuje na odpisie aktualnym. |
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
Each tool targets a distinct use case: get_board for quick board composition summary, get_entity for current full entity data, and get_entity_full for historical records. There is no ambiguity or overlap between them.
All tool names follow a consistent get_ prefix pattern with snake_case (get_board, get_entity, get_entity_full), making the naming predictable and easy to understand.
Three tools is an appropriate number for a specialized KRS data retrieval server. Each tool serves a distinct purpose covering the main query needs without being excessive or too sparse.
The tools cover the main read operations for KRS entities (current data, full history, board summary). However, a search tool by name or NIP is missing, which would be a natural complement for a complete data retrieval surface.