Skip to main content
Glama

Prawnet: Polish case law and legislation

Wyrok TSUE w polskich sądach

tsue_w_polsce
Read-onlyIdempotent

Sprawa TSUE lub Sądu UE o danej sygnaturze (metadane EUR-Lex: rodzaj, data, ECLI, hasła, linki EUR-Lex i CURIA) oraz polskie orzeczenia z bazy Prawnet, których tekst wymienia tę sygnaturę: liczba, odsetek potwierdzony na próbie, podział wg rodzaju sądu i roku, przykłady z linkami. Mierzy wzmianki, nie zgodność z wyrokiem. Baza: sądy powszechne, SN, część NSA/WSA, TK, KIO. Bez treści i nazwisk.

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": {
      "sygnatura_tsue": "<sygnatura_tsue>"
    },
    "name": "tsue_w_polsce"
  }
}

Input Schema

NameRequiredDescriptionDefault
sygnatura_tsueYesSygnatura ("C-260/18", "T-123/20") albo CELEX ("62018CJ0260"), do 40 znaków

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), the description adds substantive behavioral context: the database coverage is enumerated (common courts, SN, part of NSA/WSA, TK, KIO), so the agent knows the result is partial, and it discloses that the percentage is 'potwierdzony na próbie' (sample-confirmed) and that no ruling text or personal names are returned. The mention-vs-agreement caveat is exactly the kind of semantic warning annotations cannot carry. Only the sampling methodology and any rate/pagination limits remain unstated.

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?

Dense but front-loaded: the primary object (the EU case) comes first, the citing-rulings payload second, and the important caveats ('Mierzy wzmianki…', 'Bez treści i nazwisk') close it out. Every clause carries information; the long parenthetical metadata list is the only mildly heavy element. No filler or repetition.

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?

For a single-parameter, read-only lookup with an output schema and full annotations, the description covers what the tool returns, the database boundaries, and the interpretive limit of the metric — everything an agent needs to call it and to frame the answer. It slightly over-specifies the return payload that the output schema already defines, but nothing material 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%: the single parameter is already documented with format examples ('C-260/18', 'T-123/20'), a CELEX alternative ('62018CJ0260') and a 40-character limit. The description adds nothing about the parameter itself. With the schema doing all the work, the baseline of 3 applies.

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 precisely names the two things returned: the EU case with the given signature (with EUR-Lex metadata fields: type, date, ECLI, keywords, EUR-Lex/CURIA links) and the Polish rulings in the Prawnet database whose text cites that signature, with counts, share, breakdowns and examples. It is a nominal phrase rather than an explicit verb, but the resource and scope are unmistakable. It also implicitly separates itself from citation-lookup siblings by stating it measures mentions rather than agreement with the judgment.

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 this is the tool for 'how do Polish courts reference this CJEU case', and the note 'Mierzy wzmianki, nie zgodność z wyrokiem' usefully caps what the result can be used to claim. However, there is no explicit when-to-use/when-not statement and no named alternative (e.g. cytowania_orzeczenia or sprawdz_sygnature) for the adjacent citation-lookup needs. Guidance is adequate but left to inference.

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