Skip to main content
Glama

Prawnet: Polish case law and legislation

Opłata sądowa od pisma

oplata_sadowa
Read-onlyIdempotent

Opłata sądowa od pisma w sprawie cywilnej wg ustawy o kosztach sądowych w sprawach cywilnych (u.k.s.c.; jak kalkulatory prawnet.pl, bez bazy danych). rodzaj: pozew (art. 13: kwoty stałe do 20 000 zł, ponad — 5 % wartości przedmiotu sporu, maks. 100 000 zł), pozew w EPU i w postępowaniu nakazowym (¼), apelacja, zażalenie (⅕), sprzeciw od wyroku zaocznego (½), zarzuty od nakazu zapłaty (¾), skarga kasacyjna, wnioski w toku sprawy, sprawy rodzinne i niemajątkowe (np. rozwód), postępowanie nieprocesowe (stwierdzenie nabycia spadku, dział spadku, zasiedzenie, podział majątku), księgi wieczyste, egzekucja i pisma wolne od opłat. Wynik: opłata, rozpis kroków z podstawą każdego (ułamek, zaokrąglenie w górę do złotego — art. 21, minimum 30 zł — art. 20 ust. 1), przy pozwie także warianty EPU i nakazowy, uwagi, podstawa_prawna, stan_prawny (data weryfikacji stawek), link do kalkulatora.

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

Input Schema

NameRequiredDescriptionDefault
wpsNoWartość przedmiotu sporu (apelacja, zażalenie: zaskarżenia) w zł; wymagana przy opłatach od wartości
rodzajNoRodzaj pisma; domyślnie pozew

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the description's job is to add computation behaviour — and it does: rounding up to the whole złoty (art. 21), a 30 zł minimum (art. 20 ust. 1), EPU/nakazowy variants returned alongside the base fee, and a 'stan_prawny' verification date. It stops short of noting limits (e.g. that 'wps' is ignored for flat-fee categories), which is why it is not 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 purpose is front-loaded, but the body is one enormous sentence built from nested parentheses, and much of the category list duplicates enum values the schema already exposes. It is dense rather than padded, yet a bulleted or short-list structure would scan far better.

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?

For a legal-fee calculator with 68 enum values and an output schema, the description covers the rule set (percentage vs flat, cap, rounding, minimum), the case-type taxonomy, the extra returned variants and the legal-basis provenance field. An agent has everything needed to call it and interpret the result without further context.

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, but the description genuinely adds meaning: it maps several enum values to their statutory fractions (¼ for EPU/nakazowy, ⅕ for zażalenie, ½ for sprzeciw zaoczny, ¾ for zarzuty) and explains the flat-amount-vs-5%-with-cap rule tied to 'wps'. That is real semantic value the bare enum codes do not convey.

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?

States a specific verb+resource: computes the court fee ('opłata sądowa') for a pleading in a civil case under the u.k.s.c. act. The scope is narrowed precisely (civil, statutory basis, no database), which distinguishes it from cost/interest calculators among the siblings.

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 long enumeration of 'rodzaj' categories implicitly tells the agent which case types are supported, and the mention of 'bez bazy danych' hints at statelessness. However, it never states when NOT to use it or points to a sibling such as koszty_zastepstwa for representation costs, so routing is 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