Skip to main content
Glama

Prawnet: Polish case law and legislation

Ile trwa sprawa w sądzie

ile_trwa_sprawa
Read-onlyIdempotent

Ile trwa sprawa sądowa według opublikowanych orzeczeń: mediana dni, kwartyle (q1, q3) i 90. percentyl, n spraw i okres (lata wyroków) osobno dla każdego szczebla i instancji. Wejście: temat (np. sprawa o alimenty, frankowa, zachowek, karna, apelacja cywilna) albo kod repertorium z sygnatury. Początek sprawy szacowany z pozycji numeru sprawy w roku rejestracji (sygnatura niesie rok, nie datę wpływu); główna liczba z wyroków ostatnich 5 lat, gdy jest ich co najmniej 30. Przy kodzie repertorium także mediana od 1 stycznia roku z sygnatury (sygnatury_statystyki; dokładność: rok). Wynik: opis metody, udział spraw z szacowaną datą i pominiętych (gdy ≥ 5 %, mediana jest górną granicą). Tematy i liczby jak na stronie prawnet.pl/ile-trwa-sprawa-w-sadzie.

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

Input Schema

NameRequiredDescriptionDefault
tematNoSlug strony /ile-trwa-sprawa-w-sadzie: rodzaj sprawy (sprawa-cywilna … zazalenie) albo roszczenie (sprawy, w których sąd powołał dany przepis)
szczebelNoJeden szczebel; pominięte = wszystkie osobno
repertoriumNoZamiast temat: kod repertorium z sygnatury ("C", "Ca" — apelacje w SO, "ACa" — w SA, "RC", "P", "U", "K", "GC", "Ns"); wielkość liter ma znaczenie. Do 16 znaków

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, and the description adds real methodological context: start date is estimated from the case-number position in the registration year, the headline figure uses the last 5 years of judgments only when n ≥ 30, and when ≥5% of cases are omitted the median becomes an upper bound. That is substantive disclosure an agent cannot get from the annotations or schema, though it says nothing about rate limits or response shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is front-loaded and every sentence carries information, but the single dense block with stacked parentheticals (sygnatura year caveat, ≥30 rule, ≥5% rule) is hard to scan. The closing reference to the prawnet.pl page and 'Tematy i liczby jak na stronie…' adds little beyond the preceding text.

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 still covers the methodological caveats an agent needs to interpret the numbers correctly. Complexity is moderate and coverage is nearly complete; only explicit sibling routing is missing.

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 both enums are self-documenting, so the baseline is 3. The description adds modest value by clarifying that temat covers both case types and claim types identified by a cited provision, and by giving example topics, but it largely restates what the schema fields already declare.

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 names a specific resource and the exact metrics returned (median days, q1/q3, p90, n cases, judgment-year span, per instance level), so an agent knows precisely what the tool produces. It does not name any sibling to contrast with, so it falls short of a 5, but the scope is unambiguous against neighbors like ile_zasadzaja or termin_procesowy.

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?

It states the input alternatives (temat OR repertorium code) and notes that the repertorium path additionally produces a median from January 1 of the signature year, which is useful input-selection guidance. However, there is no explicit when-to-use/when-not versus other tools and no exclusions, so usage is only implied by the parameter discussion.

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