Skip to main content
Glama

Prawnet: Polish case law and legislation

Urzędowe rachunki bankowe

rachunki_urzedowe
Read-onlyIdempotent

Urzędowe rachunki bankowe do wpłat, każdy numer ze źródłem (URL) i datą pobrania. urzad_skarbowy: rachunki 400 urzędów skarbowych z wykazu KAS (od 1.01.2024), według urzędu i symbolu formularza; dla PIT, CIT, VAT i innych należności z rozporządzenia Dz.U. 2025 poz. 1305 — zasada mikrorachunku podatkowego i generator MF, bez wyliczania numeru. sad: rachunki opłat sądowych i zaliczek ze stron 6 sądów okręgowych i 3 rejonowych (pilotaż); inne sądy — status z odesłaniem do strony sądu i Sądowych ePłatności. oplata_skarbowa: zasada wpłaty na rachunek gminy, bez numeru.

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": {
      "typ": "<typ>"
    },
    "name": "rachunki_urzedowe"
  }
}

Input Schema

NameRequiredDescriptionDefault
typYes
nazwaNoUrząd skarbowy lub sąd: nazwa albo miejscowość, np. "Bolesławiec", "Drugi US Warszawa-Śródmieście", "SO Gdańsk XV Wydział Cywilny"
symbolNoUrząd skarbowy: symbol formularza lub tytułu płatności, np. "PCC-3", "SD-3", "PIT-37"

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds materially beyond them: data provenance (each number carries source URL and retrieval date), coverage denominators (400 tax offices from the KAS list effective 1.01.2024; 6 regional and 3 district courts on a pilot), and explicit refusal behaviors (no microrachunek computation, no gmina account number). These are exactly the limits an agent needs before promising a payment account to a user.

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?

Front-loaded with what the tool returns (accounts plus source URL and retrieval date), then organized by 'typ' value, which matches the required parameter. Dense semicolon-joined clauses make it a heavy read, but each clause contributes a distinct scope or exclusion rather than filler.

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 shape need not be spelled out, and the description still flags that results include a source URL and fetch date. Given the closed-world, read-only nature and the three-way mode split, nothing essential for correct invocation is missing.

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 67% and the 'typ' enum has no schema description, so the description carries the load by explaining what each of the three values returns and does not return. For 'nazwa' and 'symbol' it adds little beyond the existing schema descriptions and examples.

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 (official bank accounts for payments) and enumerates the three 'typ' categories with distinct scope for each, so an agent can pick the right mode without opening the schema. It does not explicitly distinguish itself from the sibling 'sprawdz_rachunek', which likely deals with verifying a given number, so sibling differentiation is only implicit.

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?

Strong conditional guidance: 'dla PIT, CIT, VAT ... zasada mikrorachunku podatkowego i generator MF, bez wyliczania numeru' tells the agent this tool will not compute a number and points to the MF generator; 'inne sądy — status z odesłaniem do strony sądu i Sądowych ePłatności' and 'oplata_skarbowa ... bez numeru' set clear exclusions. It never names an alternative sibling tool, so routing to another MCP tool 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