Skip to main content
Glama

Prawnet: Polish case law and legislation

Historia brzmienia przepisu

historia_przepisu
Read-onlyIdempotent

Historia brzmienia jednego artykułu ustawy: lista wersji (nr, od, do, typ: pierwotna | zmieniony | dodany | uchylony, ustawa zmieniająca z Dz.U., od_szacowane — data początkowa szacowana) odtworzona z łańcucha obwieszczeń o tekście jednolitym (ELI Sejmu RP), z ogłoszonymi zmianami o odroczonym wejściu w życie (przyszla = true) i liczbą orzeczeń z bazy wydanych w okresie każdej wersji. Bez treści brzmień. Pokrycie: 50 najczęściej cytowanych aktów (główne kodeksy, Konstytucja, Ordynacja podatkowa, ustawy o VAT i PIT, Pzp i in.); dla innych aktów status brak_historii (to nie znaczy, że artykuł się nie zmieniał). nr 1 to najstarsze brzmienie w bazie, niekoniecznie pierwotne brzmienie aktu; do = dzień wejścia w życie następnej wersji (granica wyłączna), null = obowiązuje nadal. Wersje dotyczą całego artykułu, nie pojedynczego paragrafu. Moc wiążącą ma tekst ogłoszony w Dzienniku Ustaw.

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": "historia_przepisu"
  }
}

Input Schema

NameRequiredDescriptionDefault
pNoBez przepis: POZYCJA w Dz.U., nie numer (k.c. 1964/93)
yNoBez przepis: rok Dz.U.
artNoBez przepis: nr artykułu ("385-1" = 385¹), do 16 znaków
przepisNoCytat ("art. 446 § 4 kc", "art. 5 ustawy o prawach konsumenta") albo potoczna nazwa ("zasiedzenie"); zamiast y, p, art. Do 160 znaków

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 already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), yet the description still adds substantial behaviour: coverage is limited to 50 acts, deferred-entry changes appear with przyszla=true, estimated start dates are flagged with od_szacowane, and 'do' is an exclusive boundary with null meaning still in force. These are exactly the interpretive details annotations cannot express.

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 core purpose and nearly every semicolon-separated clause carries a distinct caveat that prevents misreading. The single dense paragraph with nested parentheses and a long coverage list makes it harder to scan than it needs to be, but little is genuinely expendable.

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 history-lookup tool with an output schema and full annotation coverage, the description supplies everything an agent needs: database scope, semantic meaning of each version field, exclusive date boundaries, estimated vs announced dates, and the article-level granularity limit. The remaining gaps (actual wording text) are declared non-goals rather than omissions.

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 would be 3, but the description adds meaning beyond it: versions pertain to the whole article rather than an individual paragraph, and 'nr 1' is the oldest version in the database rather than necessarily the original text. Both change how an agent should interpret the art and nr parameters, though the przepis-vs-(y,p,art) switch is already fully documented in the schema.

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: the version history ('lista wersji') of a single statutory article, enumerating the returned fields (nr, od, do, typ, ustawa zmieniająca) and explicitly stating the negative scope 'Bez treści brzmień'. That negative scope cleanly separates it from a wording-retrieval sibling such as tresc_przepisu, so an agent can pick correctly without opening the schema.

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?

It gives strong conditional context: history is available only for the 50 most-cited acts, other acts return status brak_historii, and that status must not be read as 'the article never changed'. That is real when-to-use and how-to-interpret guidance. It stops short of naming an alternative tool or an explicit 'use X instead when you need the actual wording', leaving that routing to inference.

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