Skip to main content
Glama

Prawnet: Polish case law and legislation

Wyszukaj akt prawny (Dz.U., M.P.)

szukaj_aktow
Read-onlyIdempotent

Wyszukiwarka katalogu aktów prawnych Dziennika Ustaw i Monitora Polskiego (ok. 165 tys. aktów z rejestru ELI Sejmu RP, synchronizowanego codziennie). Przeszukuje tytuł i hasła przedmiotowe aktu, nie treść przepisów: najpierw wszystkie słowa frazy, potem fragmenty słów w tytule (inna forma gramatyczna), na końcu dowolne słowo (pole dopasowanie). Adres ("Dz.U. 2014 poz. 827", "DU/2014/827"), skrót ("kpc", "Pzp") albo przepis ("art. 415 k.c.") wskazuje akt wprost. Kolejność: akty obowiązujące, akty podstawowe przed nowelizacjami i obwieszczeniami, trafność. Dla każdego aktu: ELI, adres, tytuł, typ, status z ELI, obowiazuje (true / false / null = nieznane; false także przed wejściem w życie), data ogłoszenia, ma_tekst i rodzaj tekstu w bazie, URL strony aktu w Prawnet. Do 50 trafień, stronicowane (limit, offset).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fraza": "<fraza>"
    },
    "name": "szukaj_aktow"
  }
}

Input Schema

NameRequiredDescriptionDefault
typNoTyp w rejestrze ELI
frazaYesNazwa, temat, skrót albo adres aktu ("ochrona danych osobowych", "k.p.c.", "Dz.U. 2019 poz. 2019"); do 200 znaków
limitNoDomyślnie 10
offsetNoStronicowanie; offset + limit ≤ 50
tylko_obowiazujaceNotrue = tylko obowiązujące dziś (bez uchylonych, wygasłych, przyszłych)

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover safety/profile hints (readOnly, idempotent, openWorld=false); the description carries far more. It discloses the matching strategy and its fallback order (all words of the phrase, then title fragments, then any word in 'dopasowanie'), the ranking order (in-force first, base acts before amendments and obwieszczenia, then relevance), the 50-hit cap, and the status semantics including the non-obvious 'false także przed wejściem w życie' and 'null = nieznane'.

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

Conciseness4/5

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

It is front-loaded with the resource and scope, then moves to matching behavior, then ranking, then result shape — a sensible order with no filler sentences. It is dense to the point of being a single run-on block, which costs a little scannability, but each clause carries distinct information.

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

Completeness5/5

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

For a search tool with five parameters and an output schema, everything an agent needs is present: what is indexed, what is not, how matching degrades, how results are ordered, the result ceiling, and how to interpret the status flag. The per-record field list is partly redundant with the output schema but does no harm.

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 the baseline is 3 and the schema already documents every parameter including the enum. The description still earns credit by explaining what 'fraza' can plausibly contain (name, topic, abbreviation, address, provision citation) and by tying pagination to a hard 50-result ceiling, which constrains how limit/offset may be combined.

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?

The description names a specific verb and resource ('Wyszukiwarka katalogu aktów prawnych Dziennika Ustaw i Monitora Polskiego'), gives scope (~165k acts, ELI Sejmu registry, daily sync) and explicitly bounds it: it searches title and subject headings, 'nie treść przepisów'. That boundary distinguishes it from the content-lookup siblings without needing to name them.

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

Usage Guidelines4/5

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

Usage context is clear: this is the tool for locating an act by title, topic, abbreviation or citation, and it directly resolves addresses ('Dz.U. 2014 poz. 827'), abbreviations ('kpc') and provision references ('art. 415 k.c.'). No alternative tool is named for the content-search case, so the exclusion is stated as a property of this tool rather than as routing advice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources