Skip to main content
Glama

Prawnet: Polish case law and 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, UZP, trybunal.gov.pl, wybór 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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description does add genuinely useful provenance — exact counts from the Prawnet graph across named sources, explicitly 'bez AI' — which tells the agent the figures are not model estimates. It says nothing about pagination, latency, or empty-result behavior.

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 dense sentences with the core purpose front-loaded and no filler. The enumeration of statistics is long but each item is distinct information; source list is compactly parenthesized.

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 100% parameter coverage, the definition needs mainly to convey purpose and trustworthiness, which it does, including data provenance. Minor gaps: no indication of what happens for an article with zero citations or an invalid article identifier.

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?

All three parameters are fully documented in the schema at 100% coverage, including the important p-is-a-position-not-a-number rule and the superscript notation for art. The description adds no parameter-level information beyond what the schema already carries, so the baseline of 3 applies.

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?

States a concrete verb-and-resource: citation statistics for one article, and enumerates the exact outputs (total count, court-type breakdown, yearly curve, first/last ruling, co-cited provisions). The phrase 'jednego artykułu' implicitly separates it from ruling-level citation tools like cytowania_orzeczenia, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not guidance and no mention of an alternative such as trend_przepisu or orzeczenia_do_przepisu. The agent must infer from the output list that this is the 'how many times is this article cited' tool.

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