Skip to main content
Glama

Prawnet: Polish case law and legislation

Zmiany aktu prawnego

zmiany_aktu
Read-onlyIdempotent

Zmiany jednego aktu prawnego. (1) Nadchodzące: akty zmieniające z datą zmiany późniejszą niż dziś (rejestr ELI) oraz artykuły z ogłoszoną, jeszcze nieobowiązującą zmianą i jej datą (noty Kancelarii Sejmu w tekście ujednoliconym). (2) Ostatnie akty zmieniające, od najnowszych, z datą zmiany według ELI i znacznikiem po_tekscie_jednolitym (ogłoszony po najnowszym tekście jednolitym, więc tekst jednolity go nie zawiera). (3) Zmiany brzmienia artykułów między zapisanymi wersjami tekstu jednolitego: dodany / zmieniony / uchylony, fragmenty przed i po do 300 znaków; tylko ok. 230 aktów z co najmniej dwiema wersjami, tylko między nimi. Akt: y i p albo pole akt. Fakty z rejestru i z porównania tekstów, bez oceny skutków zmian.

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

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
limitNoOstatnich aktów zmieniających; domyślnie 10
publikatorNoDU (domyślnie) albo MP

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Beyond the read-only/idempotent annotations, the description discloses meaningful limits: mode (3) only covers roughly 230 acts having at least two consolidated versions, only comparisons between those versions, and snippets capped at 300 characters. It also scopes the output as 'Fakty z rejestru i z porównania tekstów, bez oceny skutków zmian', clarifying that no impact assessment is produced.

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?

The text is front-loaded with a one-line purpose followed by clearly numbered modes, so an agent can scan to the relevant case quickly. It is dense with parentheticals and register jargon (ELI, po_tekscie_jednolitym, noty Kancelarii Sejmu), which costs some readability but each clause carries substantive information.

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, return values need not be explained, and the description covers mode selection, act identification, data provenance, and coverage limitations. Minor gaps remain, such as what happens when no changes are found and how the default limit interacts with mode (1), but nothing essential for correct invocation is missing.

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 already 100%, so the baseline is 3, but the description adds one genuinely useful clarification: y and p are used together as an alternative to the single 'akt' field, which the per-parameter schema text only implies. It does not elaborate on limit or publikator defaults beyond what the schema already documents.

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 states a specific verb and resource ('Zmiany jednego aktu prawnego') and then enumerates three distinct result modes (upcoming changes, latest amending acts, article-level wording changes between consolidated versions), so an agent knows exactly what comes back. It does not, however, contrast itself with closely overlapping siblings such as porownaj_brzmienie or historia_przepisu, leaving mode (3) potentially ambiguous.

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?

Each numbered mode carries its own applicability condition ('z datą zmiany późniejszą niż dziś', 'od najnowszych', 'między zapisanymi wersjami tekstu jednolitego'), which effectively tells the agent when each result set applies. It also states how to identify the act ('Akt: y i p albo pole akt'), but gives no explicit exclusions or pointers to alternative tools.

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