Skip to main content
Glama

Prawnet: Polish case law and legislation

Decyzje Prezesa UODO

szukaj_decyzji_uodo
Read-onlyIdempotent

Decyzje Prezesa UODO z portalu orzeczenia.uodo.gov.pl: sygnatura, daty, prawomocność, przedmiot (do 300 znaków), hasła, link. Wszystkie słowa frazy muszą wystąpić; do 10 wyników od najnowszych, n = liczba trafień. Bez pełnej treści.

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": {
      "fraza": "<fraza>"
    },
    "name": "szukaj_decyzji_uodo"
  }
}

Input Schema

NameRequiredDescriptionDefault
rokNoRok wydania
frazaYesSłowa lub sygnatura

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the description is freed from that burden. It still adds real operational detail: all phrase words must match (conjunctive search), results capped at 10 sorted newest-first, 'n' reports the total hit count, and returned subject matter is truncated to 300 characters with no full text.

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?

Field inventory, matching rule, result cap and sort order are all front-loaded with no filler sentences. The telegraphic, fragmentary style ('Bez pełnej treści.') is dense but slightly less readable than connected prose.

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 two-parameter search tool with an output schema and full annotations, the description covers matching semantics, result limits, ordering and the count field — everything needed to call it correctly. It does not say whether more than 10 results can be obtained or how 'rok' interacts with the phrase, minor gaps given the output schema carries the return shape.

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 100%, so baseline is 3; the description earns an extra point by explaining that every word of 'fraza' must occur and that a case signature can be used as the query, which clarifies matching semantics the schema does not state. The 'rok' parameter is not mentioned in the description, leaving that one to the schema alone.

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 names a specific resource (UODO President decisions) and its source portal (orzeczenia.uodo.gov.pl), plus the exact fields returned (sygnatura, dates, prawomocność, przedmiot, hasła, link). This clearly separates it from the other szukaj_* siblings by corpus, even though no sibling is named explicitly and the verb 'search' is only implied by the name and matching rules.

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 by the scoping to the UODO portal and by the note that results exclude full text ('Bez pełnej treści'), which hints an agent must go elsewhere for the reasoning. But there is no explicit when-to-use vs. when-to-use-an-alternative guidance, and no prerequisites or exclusions are stated.

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