Skip to main content
Glama

Prawnet: Polish case law and legislation

Metryka aktu prawnego

informacja_o_akcie
Read-onlyIdempotent

Metryka aktu prawnego z Dziennika Ustaw lub Monitora Polskiego (rejestr ELI Sejmu RP): tytuł, typ, status ELI, akt_obowiazuje, daty (wydania, ogłoszenia, wejścia w życie, uchylenia), akty uchylające, zapowiedziane uchylenie, uwagi ELI o wejściu w życie, podstawa prawna (rozporządzenia), najnowszy tekst jednolity i lista obwieszczeń, akty zmieniające ogłoszone po najnowszym tekście jednolitym, liczba aktów zmieniających i wykonawczych, orzeczenia TK o akcie, liczba artykułów i rodzaj tekstu w bazie, linki do PDF (api.sejm.gov.pl) i strony aktu w Prawnet. Akt: y i p albo pole akt. Adres obwieszczenia o tekście jednolitym jest zamieniany na akt, którego tekst ogłasza (zapytany_adres). Gdy ELI nie odpowie, eli_dostepne = false i część pól jest pusta. Nazwa pasująca do kilku aktów: status niejednoznaczne z kandydatami. struktura: true zwraca zamiast metryki spis części, tytułów, działów i rozdziałów z zakresami artykułów lub § (bez nagłówków w tekście: status struktura_niedostepna).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "informacja_o_akcie"
  }
}

Input Schema

NameRequiredDescriptionDefault
pNoBez akt: POZYCJA w roczniku, nie numer (k.c. = 1964 poz. 93)
yNoBez akt: rok Dz.U. (lub M.P.)
aktNoAdres ("Dz.U. 1964 nr 16 poz. 93", "M.P. 2024 poz. 100"), ELI ("DU/2014/827"), skrót ("k.p.c.", "Pzp"), nazwa ("ustawa o cudzoziemcach") albo przepis ("art. 415 k.c." — jego akt); zamiast y, p. Do 200 znaków
strukturaNotrue = tylko struktura aktu (księgi, części, tytuły, działy, rozdziały, oddziały z zakresem artykułów lub §) zamiast metryki
publikatorNoDU (domyślnie) albo MP

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / struktura
      Added value: +{
      +  "description": "true = tylko struktura aktu (księgi, części, tytuły, działy, rozdziały, oddziały z zakresem artykułów lub §) zamiast metryki",
      +  "type": "boolean"
      +}
  2. Added

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already declare a read-only, idempotent, closed-world call, and the description adds real behavioral context on top: ELI failure yields eli_dostepne=false with partially empty fields, an ambiguous name yields status 'niejednoznaczne' with candidates, and a struktura request can fail with 'struktura_niedostepna' when headings are absent. The address-substitution rule (obwieszczenie resolved to the announced act, exposed as zapytany_adres) is exactly the kind of non-obvious behavior a caller needs.

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

Conciseness3/5

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

The opening sentence is front-loaded correctly, but it degenerates into a long comma-separated field inventory that largely duplicates the output schema, followed by several useful but unsegmented sentences on fallbacks and the struktura mode. Splitting return values from behavioral notes would make every sentence earn its place.

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 an output schema present the return-field enumeration is redundant, but the definition does cover the awkward cases an agent must handle: unavailable ELI, ambiguous names, missing structure, and address-to-act resolution. What remains unstated is the alternative use of the search sibling when the act is not yet identified.

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

Parameters3/5

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

Schema coverage is 100% and the schema descriptions already carry the address/ELI/abbreviation/name/statute formats, the 'pozycja not numer' caveat and the publikator enum. The description adds only the y+p-versus-akt exclusivity restated and the address-resolution behavior, so it is a modest supplement rather than a source of new parameter meaning.

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

Purpose4/5

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

The description names a specific resource ('Metryka aktu prawnego z Dziennika Ustaw lub Monitora Polskiego, rejestr ELI Sejmu RP') and enumerates the metadata it returns, so an agent knows exactly what it gets back. It does not, however, contrast itself with siblings such as szukaj_aktow or zmiany_aktu, so the 'which tool' question is answered only by inference.

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?

Usage is implied rather than stated: the text explains that an act is addressed either by 'y i p' or by the 'akt' field, and that struktura:true returns a table of contents instead of the metric. There is no explicit when-to-use/when-not statement and no pointer to the search sibling for the case where the user does not yet know the act.

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