Skip to main content
Glama
przemonides

CRU MCP Server

by przemonides

Szukaj umów w Centralnym Rejestrze Umów

rejestr_umow_search_contracts
Read-onlyIdempotent

Search contracts in the Polish Central Register of Contracts using filters like text, party name, unit, date range, and value. Returns matching contracts with total count.

Instructions

Wyszukuje umowy opublikowane w Centralnym Rejestrze Umów JSFP (rejestrumow.gov.pl) przez API Ministerstwa Finansów.

Wymaga skonfigurowanego klucza CRU_API_KEY (patrz README.md). Nie wykonuje operacji zapisu — tylko odczyt/wyszukiwanie.

⚠️ Ścieżka zapytania (CRU_SEARCH_PATH) jest niezweryfikowanym przypuszczeniem — patrz README.md, sekcja "Status weryfikacji API".

Args:

  • query (string, opcjonalny): dowolny tekst do wyszukania

  • party_name_or_nip (string, opcjonalny): nazwa strony umowy lub NIP/REGON

  • jsfp_unit_name (string, opcjonalny): nazwa jednostki publikującej

  • date_from / date_to (YYYY-MM-DD, opcjonalne): zakres daty zawarcia

  • min_value / max_value (number, opcjonalne): zakres wartości umowy w PLN

  • page (number, domyślnie 0), page_size (number, domyślnie 20, max 100)

  • response_format ('markdown' | 'json', domyślnie 'markdown')

Returns: listę pasujących umów wraz z informacją o łącznej liczbie wyników.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoNumer strony wyników, licząc od 0.
queryNoDowolny tekst do wyszukania (np. fragment przedmiotu umowy).
date_toNoData zawarcia umowy do (YYYY-MM-DD).
date_fromNoData zawarcia umowy od (YYYY-MM-DD).
max_valueNoMaksymalna wartość umowy w PLN.
min_valueNoMinimalna wartość umowy w PLN.
page_sizeNoLiczba wyników na stronę (1-100).
jsfp_unit_nameNoNazwa jednostki sektora finansów publicznych publikującej umowę.
response_formatNoFormat odpowiedzi: 'markdown' (czytelny) lub 'json' (surowe dane).markdown
party_name_or_nipNoNazwa strony umowy albo jej NIP/REGON.
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, etc. Description adds critical context: requires API key, notes unverified query path (readiness caveat), and confirms no write operations. This enriches transparency beyond annotations. Could detail error behavior or performance limits, but fine.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is efficiently structured: purpose first, then requirements/warning, then bullet-pointed parameter list. No redundant sentences, all information is relevant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 10 parameters and no output schema, description covers all parameters, mentions return format, and adds operational caveats (API key, verification status). Lacks explicit info on pagination behavior or error handling, but sufficient for a search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. Description adds grouping of related parameters (date range, value range), provides natural language explanations, and clarifies defaults. Offers some extra semantics over schema, but not deeply transformative.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool searches contracts in the Central Register of Contracts JSFP via API, distinguishes from sibling 'rejestr_umow_get_contract' by focusing on search versus retrieval, and specifies read-only operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides context for usage (requires API key, read-only) but does not explicitly indicate when to use this tool over the sibling or what alternatives exist. Implicit guidance from sibling name, but description lacks direct differentiation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/przemonides/CRU_MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server