Skip to main content
Glama

Prawnet: Polish case law and legislation

Koszty zastępstwa procesowego

koszty_zastepstwa
Read-onlyIdempotent

Koszty zastępstwa procesowego adwokata lub radcy prawnego według wartości przedmiotu sprawy: stawki minimalne z § 2 rozporządzeń MS z 22.10.2015 r. w sprawie opłat za czynności adwokackie (Dz.U. 2015 poz. 1800) i radców prawnych (Dz.U. 2015 poz. 1804), identyczne dla obu zawodów, albo niższe z § 3 ust. 1 w postępowaniu upominawczym, EPU, nakazowym i europejskim nakazowym (rodzaj: nakazowe). Także górna granica z § 15 ust. 3 (sześciokrotność stawki minimalnej, nie więcej niż wartość przedmiotu sprawy), próg wartości i tabela progów. Bez bazy danych. Wynik: stawka_minimalna, stawka_maksymalna, podstawa_prawna, stan_prawny (data weryfikacji stawek), zrodla_stawek, 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": {
      "wps": "<wps>"
    },
    "name": "koszty_zastepstwa"
  }
}

Input Schema

NameRequiredDescriptionDefault
wpsYesWartość przedmiotu sprawy w zł
rodzajNoogolne (domyślnie, § 2) albo nakazowe: upominawcze, EPU, nakazowe, europejskie nakazowe (§ 3 ust. 1; po skutecznym sprzeciwie lub zarzutach — ogólne, § 3 ust. 2)

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 establish the read-only, closed-world, idempotent profile, and the description adds real context on top: 'Bez bazy danych' signals a deterministic offline computation with no external lookup, and 'stan_prawny (data weryfikacji stawek)' discloses that results carry a verification date. It stops short of stating rounding or edge-case handling at the boundaries of the threshold table.

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?

Despite being a dense block of legal citation, it is front-loaded with the purpose and every clause earns its place: rate basis, the reduced variant, the § 15 ust. 3 cap, thresholds, and the no-database note. The trailing list of return fields is slightly redundant given the output schema, but it does not bloat the text meaningfully.

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 deterministic calculator with an output schema, the description covers the legal basis, both rate regimes, the statutory cap and the threshold table, which is enough to call it correctly. The remaining gap is routing guidance against sibling cost/calculation tools, not invocation detail.

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 wps and the rodzaj enum, including the § 3 ust. 2 fallback. The description reinforces that the rates are identical for both professions and that rodzaj='nakazowe' covers four proceeding types, but adds little semantics the schema does not already carry — baseline 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 names a specific computation (representation costs for adwokat/radca prawny) and the exact legal basis (§ 2 and § 3 ust. 1 of the 22.10.2015 MS regulations), so an agent can tell it is a rate-lookup calculator rather than a court-fee or general calculation tool. It never explicitly contrasts itself with siblings such as oplata_sadowa or policz, which keeps it from a 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?

Usage is only implied: the description explains which proceedings map to rodzaj='nakazowe' (upominawcze, EPU, nakazowe, europejskie nakazowe) and that the general § 2 rate otherwise applies, which effectively guides parameter choice. It gives no explicit when-to-use/when-not framing and no statement of when to reach for this instead of a related cost tool.

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