Skip to main content
Glama

Prawnet: Polish case law and legislation

Rachunek na białej liście VAT

sprawdz_rachunek
Read-onlyIdempotent

Czy rachunek bankowy (NRB / IBAN PL) jest na białej liście podatników VAT dla danego NIP w danym dniu (domyślnie dziś; data nie z przyszłości). Zwraca status na_liscie albo nie_na_liscie, requestId nadany przez MF jako dowód i datę sprawdzenia. Suma kontrolna rachunku jest sprawdzana lokalnie. Nie zwraca nazwy ani adresu podatnika ani jego innych rachunków. Źródło: wl-api.mf.gov.pl.

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": {
      "nip": "<nip>",
      "rachunek": "<rachunek>"
    },
    "name": "sprawdz_rachunek"
  }
}

Input Schema

NameRequiredDescriptionDefault
nipYesNIP podatnika, 10 cyfr
dataNoData sprawdzenia RRRR-MM-DD, nie późniejsza niż dziś; domyślnie dziś
rachunekYesNumer rachunku: NRB (26 cyfr) albo IBAN z prefiksem PL; spacje dozwolone

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for what it adds: the exact return statuses (na_liscie / nie_na_liscie), an MF-issued requestId serving as proof, a local checksum validation of the account number, and an explicit statement of what is NOT returned. It stops short of describing error/failure behavior or rate limits, which keeps it below 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.

Conciseness4/5

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

Dense but front-loaded: the core question opens the description, followed by return shape, exclusions, and source. Every sentence carries information, though it is delivered as one unbroken paragraph with parentheticals rather than clearly separated blocks.

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, yet the description still names the key return fields and the negative space (no name, address, or other accounts), and it discloses the data source. For a three-parameter read-only lookup, nothing an agent needs in order to call it correctly is missing.

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 description coverage is 100%, so all three parameters are already documented with formats. The description only echoes the date constraint and mentions the local checksum check on the account number; it adds no syntax or format meaning beyond the schema. Baseline 3 applies.

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-and-resource pair: checks whether a given NRB/IBAN bank account appears on the VAT whitelist for a given NIP on a given date. It also delimits scope negatively ('Nie zwraca nazwy ani adresu podatnika ani jego innych rachunków'), so an agent can tell it apart from a registry-lookup or an official-accounts-list tool without opening the schema.

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 context is implied (whitelist verification for a taxpayer's account on a date, default today, date not in the future), but there is no explicit when-to-use/when-not guidance and no sibling is named as an alternative. The agent must infer the routing itself.

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