Skip to main content
Glama

Prawnet: Polish case law and legislation

Klauzule niedozwolone (UOKiK, art. 385³ k.c.)

klauzule_niedozwolone
Read-onlyIdempotent

Klauzule niedozwolone w umowach z konsumentami: 23 punkty katalogu art. 385³ k.c. (postanowienia, które w razie wątpliwości uważa się za niedozwolone) oraz wybór 62 wpisów z rejestru klauzul niedozwolonych UOKiK (siłownie i kluby fitness, najem i pośrednictwo w nieruchomościach, umowy deweloperskie, telekomunikacja, kursy i szkolenia, sklepy internetowe, klauzule międzybranżowe) — każdy z numerem i datą wpisu, uzasadnieniem, punktem art. 385³ i linkiem do rejestru UOKiK. Wejście opcjonalne; fraza dopasowywana leksykalnie (nie ocena prawna). Od 18.04.2026 wpisy rejestru nie mają samodzielnej mocy prawnej (art. 479⁴⁵ k.p.c. przestał obowiązywać — ustawa z 5.08.2015, Dz.U. 2015 poz. 1634); pokazują linię orzecznictwa SOKiK. Także liczba orzeczeń bazy Prawnet powołujących art. 385¹ i 385³ k.c. To wybór wpisów, nie cały rejestr.

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

Input Schema

NameRequiredDescriptionDefault
frazaNoSłowa ("zmiana regulaminu", "kaucja") albo tekst klauzuli; do 500 znaków. Dopasowanie po słowach klauzuli i uzasadnienia wpisu
limitNoWpisów rejestru; domyślnie 20
punktNoPunkt katalogu art. 385³ k.c.: ten punkt i wpisy rejestru wskazujące go w uzasadnieniu
offsetNoStronicowanie wpisów
sektorNoBranża (najem = też pośrednictwo w nieruchomościach; ogolne = międzybranżowe): jej wpisy, po nich międzybranżowe

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, closed-world behavior. The description adds substantial context beyond them: it discloses that only 62 selected register entries are included, explains the post-18.04.2026 loss of independent legal force of register entries, and warns that matching is lexical rather than legal analysis.

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 content is front-loaded and information-dense, but it is delivered as a long single paragraph with exact statutory citations and output-field details that the output schema already covers. It would be more scannable as short labeled sections.

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 read-only reference tool with an output schema and rich annotations, the definition covers provenance, scope limits, and the important legal-status caveat. Minor gaps remain around pagination across the 62-entry selection and behavior when no filters are supplied, though the schema fills most of that.

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 coverage is 100%, so the schema already documents all five parameters, including the sector enum and point range. The description adds the useful caveat that fraza is matched lexically, but otherwise mostly restates catalog/register scope rather than parameter behavior.

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 legal resource and enumerates its two components: the 23-point art. 385³ catalog and 62 selected UOKiK register entries, plus related ruling counts. It does not explicitly distinguish itself from sibling tools such as orzeczenia_do_przepisu or szukaj_wiedzy, so it falls short of 5.

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?

It states that input is optional and that phrase matching is lexical rather than a legal assessment, which sets expectations for querying. It gives no explicit when-to-use/when-not-to-use guidance or alternative-tool routing, so usage is only implied.

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