Skip to main content
Glama

Prawnet: Polish case law and legislation

Orzeczenia powołujące przepis

orzeczenia_do_przepisu
Read-onlyIdempotent

Lista orzeczeń, które powołują dany artykuł ustawy (graf przepis→orzeczenie Prawnet), od najnowszych, z liczbą wg rodzaju sądu. Wejście: adres Dz.U. aktu (y, p) i numer artykułu. Orzeczenia POWOŁUJĄ przepis — narzędzie nie mówi, co w nim orzekły. Przepisy cytowane rutynowo (koszty, procedura — np. art. 98 k.p.c. w 28 % wszystkich orzeczeń, art. 233 k.p.c., art. 624 k.p.k.) zwracają pole uwaga: lista nie oznacza, że orzeczenie dotyczy tego przepisu merytorycznie.

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": "orzeczenia_do_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); do 16 znaków
sadNoOpcjonalny filtr rodzaju sądu (ADMINISTRATIVE = NSA/WSA — tylko wybór orzeczeń)
limitNoIle orzeczeń zwrócić (1–50); pominięte = 10

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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); do 16 znaków"New value: +"Numer artykułu: \"415\", \"178a\", \"385-1\" (indeks górny jako -N); do 16 znaków"
    • 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 / 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

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description correctly focuses on semantics: the citation graph is weak evidence, and heavily cited procedural articles trigger a `uwaga` field. It adds real context, but says nothing about result volume, pagination, or what happens when the graph has no entry.

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?

Three sentences, front-loaded with the operation and then the critical caveat. The parenthetical listing art. 98, 233 and 624 k.p.c./k.p.k. with the 28% figure is slightly heavy but directly supports the warning, so it largely earns its space.

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?

With an output schema present, the description need not explain return values, and annotations carry the safety profile. What remains — the meaning and limits of the provision→ruling relation — is exactly what the description supplies, including the `uwaga` flag caveat.

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 already documents y, p with concrete examples, the article-number format with superscript notation, the court enum, and the limit default. The description only restates that the input is the Dz.U. address plus article number, adding no meaning beyond 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?

States a specific verb and resource: a list of rulings that cite a given article of a statute, ordered newest-first with a count by court type. It further scopes itself negatively ('Orzeczenia POWOŁUJĄ przepis — narzędzie nie mówi, co w nim orzekły'), which separates it from interpretation-oriented siblings even without naming 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?

The description makes the use case clear (find rulings citing an article) and warns strongly against over-reading results for routinely cited provisions. It stops short of naming an alternative tool for the 'what did the court rule on this provision' question, so the negative guidance is implicit rather than routed.

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