Skip to main content
Glama

Prawnet: Polish case law and legislation

Losy orzeczenia (utrzymane, zmienione, uchylone)

losy_orzeczenia
Read-onlyIdempotent

Losy orzeczenia według bazy Prawnet: czy sąd wyższej instancji je utrzymał, zmienił czy uchylił (los, los_opis, zakres: całość lub część), z dowodem: orzeczenie rozstrzygające (sygnatura, sąd, data, URL, jego los), cytat sentencji do 240 znaków, źródło ustalenia. Ponadto: orzeczenia, o których losach rozstrzygnęło to orzeczenie; cytowane_n, cytuje_n, cytowane_poza_n; percentyl i poziom autorytetu (PageRank); najnowsze i najwyżej oceniane orzeczenia cytujące. Wejście: id albo sygnatura (z sądem przy numerze wielu sądów). los = brak_danych (los_znany = false): losu nie ustalono — brak w bazie orzeczenia rozstrzygającego albo rozstrzygnięcia sprzeczne (dowody_sprzeczne; wszystkie w dowody); to nie informacja o prawomocności ani o braku zaskarżenia. Losy ustalane automatycznie z sentencji; znane dla niespełna 2 % orzeczeń bazy. Status: niejednoznaczne (kandydaci z id), nie_znaleziono. Bez składu sędziowskiego.

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

Input Schema

NameRequiredDescriptionDefault
idNoId orzeczenia Prawnet (koniec adresu strony, np. 168311 w sn-iii-czp-100-14-168311, albo z list wyników); wtedy sygnatura i sad pomijane
sadNoPrzy sygnaturze noszonej przez kilka sądów: nazwa lub miasto ("SA w Łodzi", "SN", "WSA w Gdańsku") albo rodzaj (COMMON, SUPREME…); nierozpoznany pomijany (ostrzezenia)
limitNoOrzeczeń cytujących w każdej z dwóch list (najnowsze, wg autorytetu); domyślnie 5
sygnaturaNoBez id: sygnatura w dowolnej pisowni ("I ACa 1890/22"); z tekstu brana pierwsza. Do 200 znaków

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Id orzeczenia Prawnet (koniec adresu strony, np. 168311 w sn-iii-czp-100-14-168311; także z list wyników); wtedy sygnatura i sad pomijane"New value: +"Id orzeczenia Prawnet (koniec adresu strony, np. 168311 w sn-iii-czp-100-14-168311, albo z list wyników); wtedy sygnatura i sad pomijane"
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

With readOnly/idempotent/openWorld=false already covered by annotations, the description adds substantial context the annotations cannot: results are derived automatically from the sentencja, coverage is under 2% of the base, and los=brak_danych means evidence is missing or contradictory — explicitly 'not information about finality or lack of appeal'. It also discloses the niejednoznaczne/nie_znaleziono statuses, preventing the most likely misreading of an empty result.

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?

Purpose is front-loaded, but the body is a single dense run-on block of semicolon- and parenthesis-chained clauses with no line breaks or grouping. Much of the middle section duplicates what the output schema already documents (field-by-field return inventory), so length is not fully earned.

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 tool with four optional parameters, ambiguous identifiers, and a high risk of misinterpreted empty results, the description covers inputs, disambiguation, degraded states, coverage limits, and caveats. An output schema exists, so the enumerated return fields are redundant but not harmful to completeness.

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%, so the schema already carries the parameter meanings; the description only restates the id-or-sygnatura relationship and the sad disambiguation rule. The limit parameter (citing lists per list, default 5) is never mentioned in the description, so no meaning is added beyond the structured fields.

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?

The opening clause states the exact resource and the exact question answered: whether a higher court 'utrzymał, zmienił czy uchylił' the judgment, per the Prawnet base. It then enumerates the returned evidence (rozstrzygające orzeczenie, cytat sentencji, źródło) and explicitly scopes out judicial panel composition, which separates it from citation-oriented siblings such as 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?

Usage is implied rather than stated: the reader infers 'call this when you need the appellate fate of a known judgment', and the entry rules (id preferred, sygnatura plus sad when the number is shared) are given. There is no explicit when-not guidance, no named alternative, and only the trailing 'Bez składu sędziowskiego' acts as a scope exclusion.

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