Skip to main content
Glama

Pelnora: Polish law and court rulings

Orzeczenia pod sygnaturą

search_docket
Read-only

Wszystkie dokumenty pod sygnaturą (dopasowanie dosłowne; gdy go brak, bez rozróżniania wielkości liter, z polem docketMatch: "case-insensitive" i sygnaturą pozycji w brzmieniu źródła; I CZ to SN, I Cz to sąd okręgowy): orzeczenia i np. zagadnienie prawne rozstrzygane pod tą samą sygnaturą; każda pozycja ma documentKind (ruling = orzeczenie). Podsumowanie per sąd (courts), filtr typu sądu i sądu, strony kursorem. Brak orzeczenia SN pod sygnaturą SN: coverageHint (rok z sygnatury, szacowane pokrycie SN w coveragePercent, gdy znane, i zdanie dla czytelnika); gdy pod sygnaturą jest tylko orzeczenie SN wycofane, withdrawnNote zamiast coverageHint.

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": {
      "docket": "<docket>"
    },
    "name": "search_docket"
  }
}

Input Schema

NameRequiredDescriptionDefault
courtNokod sądu (courtCode) albo nazwa
cursorNonextCursor z poprzedniej strony
docketYessygnatura, np. III CZP 38/24
courtTypeNotyp sądu

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so a lower score is warranted; the description goes beyond them by disclosing the two-stage matching behavior, the docketMatch marker, documentKind per result, per-court summaries, and cursor pagination. It also documents edge behaviors: coverageHint with year and coveragePercent when an SN ruling is missing, and withdrawnNote when only a withdrawn SN ruling exists. It does not state result ordering or what happens when nothing matches at all, which keeps it from a 5.

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 core purpose is front-loaded, so an agent knows within the first clause what the tool does. However, the single run-on sentence with nested parentheses, quoted field names, and inline caveats is dense and hard to scan. Several of the parenthetical details would read better as separate short sentences.

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?

There is no output schema, and the description compensates by naming the key returned fields (courts summary, documentKind, docketMatch, coverageHint, coveragePercent, withdrawnNote). With one required and three optional parameters, all four are accounted for in the narrative. Nothing essential to calling 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?

With schema coverage at 100%, the baseline is 3, but the description adds genuine meaning: it names the court type and court filters ('filtr typu sądu i sądu') and cursor paging ('strony kursorem'), tying the optional parameters to behavior. It also explains docket normalization, which the schema only illustrates with an example. The mapping is slightly implicit since parameter names are not used literally.

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 gives a specific verb and resource: it returns all documents filed under a given docket signature (sygnatura), including rulings and legal questions decided under the same number. That is concrete enough for an agent to distinguish this from get_ruling, which the description never names, so sibling differentiation is only implicit. The parenthetical note on 'I CZ' vs 'I Cz' adds precision that prevents lookup by the wrong court.

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 text describes the matching strategy (exact first, then case-insensitive with docketMatch), which implies this is a lookup-by-signature tool, but it never states when to prefer it over get_ruling or rulings_for_provision. There are no exclusions, prerequisites, or failure conditions that tell the agent when to choose another tool. The reader must infer that single-document retrieval belongs to a sibling.

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