Skip to main content
Glama

Pelnora: Polish law and court rulings

Orzeczenia powołujące przepis

rulings_for_provision
Read-only

Wyłącznie ORZECZENIA (documentKind: ruling) powołujące akt albo przepis (z jednostkami podrzędnymi), najnowsze pierwsze; filtr typu sądu; strony kursorem (nextCursor). Każda pozycja ma textStatus i citation. Zagadnienia prawne, wnioski o podjęcie uchwały i dokumenty nieustalonego rodzaju nie są orzeczeniami: tu tylko ich licznik (otherDocuments). Ze stan: tylko orzeczenia wydane do tego dnia włącznie. Przy unit każda pozycja ma provisionAtJudgmentDate: wywołanie get_provision z stan = data orzeczenia (brzmienie przepisu w dniu orzeczenia; przed pokryciem tekstu stan NOT_COVERED; numer przepisu jak w powołaniu, bez mapy przenumerowań). Zapis przepisu, którego parser nie rozpoznaje: błąd z powodem, ten sam co odpowiedź 400 trasy /orzeczenia/by-provision.

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": {
      "eli": "<eli>"
    },
    "name": "rulings_for_provision"
  }
}

Input Schema

NameRequiredDescriptionDefault
eliYesELI aktu: DU/1974/141 albo DU-1974-141 (Kodeks pracy)
stanNodzień RRRR-MM-DD: orzeczenia wydane do tego dnia włącznie (bez niego: wszystkie)
unitNoprzepis (opcjonalnie); bez niego orzeczenia powołujące akt. Indeks górny numeru: „art. 385^1” albo „art. 385(1)” (także cyfrą w indeksie górnym Unicode), ścieżka arti(385^1); zapis bez znaku indeksu („art. 3851”) oznacza artykuł o takim numerze. Nawias tuż po numerze, bez spacji, to zawsze indeks górny („art. 22(1)” = art. 22^1), nigdy ust. ani §.
limitNo
cursorNonextCursor z poprzedniej strony
courtTypeNotyp sądu

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations the description discloses result ordering, cursor paging via nextCursor, per-item fields (textStatus, citation, provisionAtJudgmentDate), the stan cutoff semantics (judgments issued up to and including that day), the NOT_COVERED coverage state, and the failure mode for unparseable provision strings (same error as the route's HTTP 400). That is substantive behavioral context an agent cannot get from the annotations.

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?

Front-loaded with the hard scoping constraint ('Wyłącznie ORZECZENIA ... najnowsze pierwsze'), then paging, then exclusions, then the per-item semantics, so readers can stop early. It is a single dense block of semicolon-separated clauses; readability would improve with light structuring, but no sentence is padding.

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?

There is no output schema, and the description compensates by describing the return payload (nextCursor, textStatus, citation, provisionAtJudgmentDate, otherDocuments counter) and the error contract. For a six-parameter, filtered listing tool with a single required argument, nothing needed to call it correctly appears to be 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?

Schema coverage is high (83%) and already documents eli, stan, unit and cursor formats, so the description adds rather than duplicates: it explains the semantic effect of omitting unit (judgments citing the act), what changes when unit is supplied (provisionAtJudgmentDate, get_provision with stan = judgment date), and the stan cutoff. It adds little new for courtType and limit beyond what the schema shows.

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 first clause names a specific verb-like operation and resource ('Wyłącznie ORZECZENIA ... powołujące akt albo przepis') and pins the scope with the internal document kind discriminator (documentKind: ruling). It also states ordering (newest first), a facet (court type) and paging (cursor), so an agent can distinguish it from get_ruling and get_provision 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 Guidelines5/5

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

It explicitly delineates what is out of scope (zagadnienia prawne, wnioski o podjęcie uchwały, documents of undetermined kind) and explains that these are only surfaced as a count in otherDocuments. It also names the follow-up alternative get_provision for retrieving the provision text as of the judgment date, i.e. when to use which 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