Skip to main content
Glama

Prawnet: Polish case law and legislation

Termin procesowy

termin_procesowy
Read-onlyIdempotent

Ostatni dzień terminu procesowego lub materialnego od zdarzenia, np. doręczenia (jak kalkulator prawnet.pl, bez bazy danych). zdarzenie: gotowy termin (sprzeciw, zarzuty, apelacja cywilna i karna, zażalenie, skarga kasacyjna, skarga do WSA, odwołanie i in.) albo własny: ilosc + jednostka + rezim. Reguły: w terminie w dniach nie liczy się dnia zdarzenia; termin w tygodniach, miesiącach lub latach kończy się w dniu odpowiadającym datą (brak takiego dnia — ostatni dzień miesiąca); koniec w sobotę lub dzień ustawowo wolny przechodzi na następny dzień roboczy. Wynik: koniec terminu, dzień tygodnia, przesunięcia z nazwami świąt, podstawa_prawna, zasada zachowania terminu przy nadaniu pocztowym, stan_prawny, link do kalkulatora.

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": {
      "data": "<data>"
    },
    "name": "termin_procesowy"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesDzień zdarzenia (doręczenia, ogłoszenia), RRRR-MM-DD
iloscNoWłasny termin: długość; najwyżej 3650 dni, 520 tygodni, 360 miesięcy, 30 lat
rezimNoWłasny termin: przepisy o obliczaniu; domyślnie kpc
jednostkaNoWłasny termin: jednostka
zdarzenieNoGotowy termin (długość i reżim); zamiast ilosc, jednostka, rezim

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare a safe, idempotent, local read (readOnlyHint, idempotentHint, openWorldHint=false), so the safety profile is covered. The description adds real value by stating the computation rules (day not counted, month-end fallback, holiday shift to next business day) and the returned fields, though it does not discuss edge cases like invalid dates.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then the ready-made-vs-custom input choice, then the accounting rules, then outputs. It is a dense single block but each sentence carries distinct information; nothing wastes space.

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?

An output schema exists, so return values needn't be explained, yet the description still names the result shape (koniec terminu, dzień tygodnia, przesunięcia, podstawa_prawna, link). For a rules-driven calculation tool, the description is complete enough to call correctly.

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% with enums, so the baseline is 3. The description nonetheless adds the crucial either/or semantics, making explicit that zdarzenie supersedes the ilosc/jednostka/rezim triple and sketching the legal regimes, which meaningfully clarifies how parameters interact beyond the schema.

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: computing the last day of a procedural/material deadline from an event. It explicitly positions itself as a standalone calculator ('jak kalkulator prawnet.pl, bez bazy danych'), which distinguishes it from data-backed siblings like przedawnienie or ile_trwa_sprawa.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly explains the two input modes: pick zdarzenie for a ready-made deadline (sprzeciw, apelacja, skarga kasacyjna, etc.) or supply ilosc+jednostka+rezim for a custom one. It does not explicitly name sibling tools or when-not-to-use, so it falls short of full alternative routing.

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