Skip to main content
Glama

Prawnet: Polish case law and legislation

Rozstrzygnięcie orzeczenia

wynik_orzeczenia
Read-onlyIdempotent

Etykieta rozstrzygnięcia jednego orzeczenia bazy Prawnet (id albo sygnatura, opcjonalnie z sądem): wynik (uwzględnienie, częściowe, oddalenie, odrzucenie, umorzenie, uchylenie i przekazanie, zmiana, utrzymanie w mocy) z opisem, wynik scalony ze statystyk, instancja, wynik środka odwoławczego, rodzaj roszczenia, kwota zasądzona (tylko przy rozstrzygnięciu zasądzającym, bez kosztów procesu i przyrostów) i żądana, pewność etykiety (wysoka / srednia / niska) i jej źródło (regula / llm = model AI). Wyrok TK: zgodność lub niezgodność z aktem wyższego rzędu. Etykiety wyprowadzone automatycznie i walidowane na próbie; wynik zawiera zastrzeżenie o trafności i pokryciu. Brak etykiety (ma_wynik = false) nie mówi nic o wyniku sprawy. Sygnatura pasująca do kilku orzeczeń: lista kandydatów z id. Bez treści orzeczenia i składu sądu.

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

Input Schema

NameRequiredDescriptionDefault
idNoId orzeczenia Prawnet (koniec adresu strony, np. 168311 w sn-iii-czp-100-14-168311)
sadNoSąd przy sygnaturze ("SA w Łodzi", "SN"), gdy numer nosi kilka sądów. Do 120 znaków
sygnaturaNoZamiast id: sygnatura, np. "I ACa 1890/22". Do 200 znaków

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Far beyond the annotations, it discloses that labels are auto-derived and sample-validated, carry a disclaimer about accuracy and coverage, and include a confidence level and provenance (regula vs llm = AI model). It also warns that ma_wynik = false says nothing about the case outcome, that awarded amounts exclude costs and increments, and that multi-match signatures yield candidates. These are exactly the caveats an agent needs to avoid misreporting results.

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 purpose is front-loaded and most content earns its place, including the valuable caveats. However, it is delivered as one dense run-on with slash- and parenthesis-separated enumerations, which makes the outcome taxonomy and the disclaimers hard to scan. Bulleting the returned facets versus the caveats would improve it markedly.

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?

Although an output schema exists, the description supplies the semantics the schema cannot: what each label means, what the confidence/source fields imply, why an awarded amount excludes costs, and how multi-candidate signatures behave. For a single-record lookup of this complexity, nothing an agent needs in order to call it and interpret the result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage the schema already documents all three parameters, so the baseline is 3; the description adds meaning by framing id vs sygnatura as alternatives ('id albo sygnatura, opcjonalnie z sądem') and explaining that a signature matching several judgments returns a candidate list with ids. It does not clarify edge cases such as passing sad without sygnatura.

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?

States a specific operation on a specific resource: the ruling label ('etykieta rozstrzygnięcia') of a single judgment in Prawnet, keyed by id or case signature. It enumerates the returned facets (outcome, instance, appeal outcome, claim type, awarded and requested amounts, confidence, source) and explicitly scopes out what siblings like full-text tools would provide ('Bez treści orzeczenia i składu sądu'), so an agent can tell it apart 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 implied rather than stated: it shows you query by id or by signature with an optional court name, and that a signature hitting multiple judgments returns a candidate list with ids. It never says when to prefer this over szukaj_orzeczen or losy_orzeczenia, nor any prerequisites. The negative scoping ('no judgment content or court composition') gives some directional help but is not explicit when-to-use guidance.

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