Skip to main content
Glama

Prawnet: Polish case law and legislation

Treść przepisu (tekst ujednolicony)

tresc_przepisu
Read-onlyIdempotent

Tekst jednego artykułu ustawy (albo paragrafu rozporządzenia: art "§ 2") z tekstu ujednoliconego Kancelarii Sejmu (ELI); rozporządzenia — z najnowszego obwieszczenia o tekście jednolitym, a bez niego z tekstu pierwotnego (pole zrodlo; tekst_pierwotny_zmieniany = tekst nieaktualny). obowiazuje_na = dzień, na który tekst obowiązuje (null = nie wiemy); przyszla_zmiana = ogłoszone, jeszcze nieobowiązujące zmiany. akt_obowiazuje = false: akt uchylony (uchylony_od, uchylony_przez). status_artykulu: uchylony / pominiety (nie uchylony) / utracil_moc. Brzmienie na dzień: pole data (RRRR-MM-DD) — historia wersji dla 50 najczęściej cytowanych aktów (główne kodeksy, Konstytucja, Ordynacja podatkowa, ustawy o VAT i PIT, Pzp i in.), wynik w brzmienie_na_dzien (przybliżone); inne akty — tekst aktualny z uwagą. Monitor Polski: publikator "MP".

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": {
      "y": "<y>",
      "p": "<p>",
      "art": "<art>"
    },
    "name": "tresc_przepisu"
  }
}

Input Schema

NameRequiredDescriptionDefault
pYesPOZYCJA w Dz.U. (nie numer): k.c. 1964/93, k.p.c. 1964/296, k.k. 1997/553, k.p.k. 1997/555, k.p. 1974/141, k.r.o. 1964/59, k.s.h. 2000/1037, k.p.a. 1960/168, Pzp 2019/2019
yYesRok Dz.U. (np. 1997 dla k.k.)
artYesNumer artykułu: "415", "178a", "385-1" (indeks górny jako -N; także "18³ca") albo paragraf rozporządzenia ("§ 2", "par. 2"); do 16 znaków
dataNoOpcjonalnie dzień RRRR-MM-DD: brzmienie z tego dnia (brzmienie_na_dzien); bez data tekst aktualny
publikatorNoDU (domyślnie) albo MP — Monitor Polski, np. Regulamin Sejmu: y 1992, p 185

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / art / description
      Previous value: -"Numer artykułu w formie URL: \"178a\", \"415\", \"385-1\" (indeks górny jako -N; także \"18³ca\"), albo paragraf rozporządzenia: \"§ 2\", \"par. 2\"; do 16 znaków"New value: +"Numer artykułu: \"415\", \"178a\", \"385-1\" (indeks górny jako -N; także \"18³ca\") albo paragraf rozporządzenia (\"§ 2\", \"par. 2\"); do 16 znaków"
    • changedInput schema / properties / data / description
      Previous value: -"Opcjonalnie: dzień RRRR-MM-DD — brzmienie obowiązujące tego dnia (pole brzmienie_na_dzien). Bez data: tekst aktualny."New value: +"Opcjonalnie dzień RRRR-MM-DD: brzmienie z tego dnia (brzmienie_na_dzien); bez data tekst aktualny"
    • changedInput schema / properties / p / description
      Previous value: -"Pozycja w Dzienniku Ustaw (y/p): k.c. 1964/93, k.p.c. 1964/296, k.k. 1997/553, k.p.k. 1997/555, k.p. 1974/141, k.r.o. 1964/59, k.s.h. 2000/1037, k.p.a. 1960/168, Pzp 2019/2019 — POZYCJA, nie numer Dz.U."New value: +"POZYCJA w Dz.U. (nie numer): k.c. 1964/93, k.p.c. 1964/296, k.k. 1997/553, k.p.k. 1997/555, k.p. 1974/141, k.r.o. 1964/59, k.s.h. 2000/1037, k.p.a. 1960/168, Pzp 2019/2019"
    • changedInput schema / properties / publikator / description
      Previous value: -"Dziennik Ustaw (\"DU\", domyślnie) albo Monitor Polski (\"MP\" — np. Regulamin Sejmu: y 1992, p 185)"New value: +"DU (domyślnie) albo MP — Monitor Polski, np. Regulamin Sejmu: y 1992, p 185"
    • changedInput schema / properties / y / description
      Previous value: -"Rok Dziennika Ustaw (np. 1997 dla Kodeksu karnego)"New value: +"Rok Dz.U. (np. 1997 dla k.k.)"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "citations": {
      +      "type": "array"
      +    },
      +    "status": {
      +      "type": "string"
      +    },
      +    "wersja_danych": {
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the bar is lower. The description nonetheless adds real caveats beyond them: historical wording is only available for the 50 most-cited acts and is approximate ('przybliżone'), other acts return current text with a note, null 'obowiazuje_na' means unknown, and revoked acts are flagged. It does not mention rate limits or auth, but those are not implied here.

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?

It is a single dense block of semicolon-separated clauses that reads like a data dictionary rather than a front-loaded purpose statement. Every clause carries information, but the caveats about return fields crowd out the core 'what this does' sentence and the abbreviations hurt scanability.

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?

For a read-only lookup with five parameters and a declared output schema, the definition covers the important edge cases: outdated texts, revoked acts, article status values, approximate historical wording, and MP citations. It is close to complete, though it spends effort restating return fields that the output schema already supplies.

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 3 is the baseline, but the description adds meaning by tying 'data' to the output field brzmienie_na_dzien and its approximate nature, and by noting the MP publikator case. The 'art' formats (including '§ 2' and superscript notation) are largely duplicated from the schema.

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 opens with a specific verb-and-resource statement: the text of a single statute article or regulation paragraph from the Sejm's consolidated text (ELI). It also clarifies that regulations come from the latest consolidated proclamation or, failing that, the original text. It does not explicitly contrast itself with siblings like historia_przepisu or porownaj_brzmienie, so it falls short of a 5.

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: passing 'data' yields the wording on that day, omitting it yields the current text, and 'publikator' switches to Monitor Polski. There is no explicit when-to-use/when-not guidance or named alternative for version history or comparative analysis.

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