Skip to main content
Glama

Prawnet: Polish case law and legislation

Trend cytowań przepisu

trend_przepisu
Read-onlyIdempotent

Roczna krzywa orzeczeń powołujących dany artykuł (od 2010 r.): n, udzial_pct (część wszystkich orzeczeń korpusu z tego roku), wolumen korpusu i z-score roku. Osobno ostatni pełny rok: n, udział, z-score (Poisson, znormalizowany wolumenem korpusu: kwartały roku wobec 8 poprzednich kwartałów, standaryzowany wg rodzaju sądu), kierunek (rosnacy przy z ≥ 2, malejacy przy z ≤ −2, stabilny; za_malo_danych, gdy rok ma mniej niż 30 orzeczeń) i zmiana udziału rok do roku (tylko przy co najmniej 30 orzeczeniach w obu latach); do tego rok szczytowy. Bieżący rok jest oznaczony jako niepełny. Krzywa jest dla artykułów z co najmniej 10 orzeczeniami. Dane z tabeli trendów Prawnet (przeliczana okresowo), bez AI.

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": "trend_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/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior, while the description adds substantial context beyond them. It discloses that data comes from Prawnet's periodically recalculated trend table, that no AI is used, that the current year is incomplete, and that direction labels depend on specific z-score and minimum-ruling thresholds.

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 description is front-loaded with the core purpose and uses a dense but readable technical paragraph. It spends several clauses enumerating output fields even though an output schema exists, but those clauses also carry methodology and threshold semantics that are not merely schema restatements.

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 complex analytical tool, the description supplies the data source, recency caveat, minimum-article threshold, z-score normalization details, direction thresholds, and incomplete-year handling. With a fully described input schema and an output schema present, this is sufficient context for correct invocation.

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%, so the input schema already explains p, y, art, and przepis in detail. The description says the curve is for a given article but does not add syntax, format, or selection guidance beyond what the schema provides, 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?

The description states a specific resource and output: an annual curve of rulings citing a given legal article from 2010, with named metrics such as n, udzial_pct, corpus volume, and z-score. It is clearly about citation-trend analysis rather than retrieving ruling text or a ruling list, but it does not explicitly distinguish itself from siblings like historia_przepisu or cytowania_orzeczenia.

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?

The description implies the use case by defining the annual citation curve and its thresholds, but it gives no explicit when-to-use or when-not-to-use guidance. It also does not name alternative sibling tools, so an agent must infer that this is for trend analysis rather than provision history or ruling retrieval.

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