Skip to main content
Glama

Prawnet — Polish case law & legislation

Art. X w liczbach

przepis_w_liczbach
Read-onlyIdempotent

Statystyka cytowań jednego artykułu: łączna liczba orzeczeń, podział wg rodzaju sądu, krzywa roczna, pierwsze i ostatnie orzeczenie, przepisy najczęściej powoływane razem z nim. Liczby są dokładnymi zliczeniami z grafu Prawnet (dane SAOS, Portal Orzeczeń, UZP, trybunal.gov.pl, NSA/WSA z CBOSA, repozytorium SN repozytorium2.sn.pl), bez AI.

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

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

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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety is covered. The description adds real context beyond that: counts are exact tallies from the Prawnet graph, with the specific source corpora (SAOS, Portal Orzeczeń, CBOSA, SN repository) and the explicit note that no AI estimation is involved — a meaningful trust signal for a statistics endpoint.

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?

Two sentences, metrics front-loaded before provenance. The long parenthetical source inventory is dense but earns its place as credibility evidence; it could be trimmed slightly without loss.

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 and full schema coverage, the agent has everything needed to invoke and interpret results; the description supplements with data provenance and the exactness guarantee. Only the lack of routing guidance toward alternative tools keeps it below 5.

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 description coverage is 100% and the schema itself explains the non-obvious 'pozycja w Dz.U.' parameter with worked examples and the superscript notation for article numbers. The description adds no parameter information beyond that, so baseline 3 applies.

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?

Opens with a specific verb+resource: 'Statystyka cytowań jednego artykułu', then enumerates exactly what is computed (total rulings, breakdown by court type, yearly curve, first/last ruling, co-cited provisions). An agent can tell this apart from siblings like cytowania_orzeczenia (a judgment) or orzeczenia_do_przepisu (a list) 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: it is a statistics tool for a single article of law. There is no explicit 'use this when…' clause, no statement of when to prefer orzeczenia_do_przepisu or historia_przepisu instead, and no prerequisites mentioned.

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