Skip to main content
Glama

Check bank account with the tax authority

check_registered_bank_account
Read-onlyIdempotent

Checks live whether a bank account is reported to the tax authority for a given taxpayer: Poland (Ministry of Finance white list, 'Wykaz podatników VAT'; the answer carries the ministry's identifier of the query, requestId) or Czechia (register of VAT payers, published accounts, with the flag 'nespolehlivý plátce' / unreliable VAT payer). It shows whether the account is reported for this taxpayer; it does not prove who owns the account, and 'not registered' is a hint, not a judgement. Poland: the NIP and the account are sent to the ministry. Czechia: only the DIČ is sent to the register; the account is compared locally with the published list.

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": {
      "country": "<country>",
      "tax_id": "<tax_id>",
      "account": "<account>"
    },
    "name": "check_registered_bank_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
tax_idYesPL: NIP (10 digits, with or without PL and dashes). CZ: DIČ (CZ followed by 8 to 10 digits).
accountYesThe bank account: IBAN, or the national form (PL: 26-digit NRB; CZ: prefix-number/bank code, e.g. 19-2000145399/0800).
countryYesPL (Poland) or CZ (Czechia).
with_receiptNoOptional, default false. Set true only when the user asks for a signed receipt of this check for their files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly, openWorld, idempotent, non-destructive), the description discloses that the check is live, exactly what data leaves the system per country, that the Polish answer carries a requestId, and that the Czech result includes the 'nespolehlivý plátce' flag. It also scopes the claim honestly: registration does not prove ownership.

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?

The core purpose and the two country branches are front-loaded, and every clause carries information. It is dense but not padded; only the trailing Poland/Czechia restatement repeats material already implied earlier, slightly reducing tightness.

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?

With no output schema, the description steps in to describe return content (requestId, unreliable-payer flag) and to bound interpretation. Combined with the fully documented 4-parameter schema and read-only annotations, an agent has everything needed to call this 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%, so the baseline is 3, but the description adds real meaning by tying country selection to which identifier and payload are used (NIP vs DIČ, remote query vs local comparison). The optional with_receipt parameter is not mentioned in the description, leaving that one gap.

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?

The description opens with a specific verb and resource ('Checks live whether a bank account is reported to the tax authority for a given taxpayer') and then enumerates the two supported jurisdictions with their source registers. This is clearly distinguishable from siblings like check_iban (format) or check_payment_details, because it names the authority-reporting question it answers.

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?

It sets clear usage context by explaining the per-country mechanics (PL sends NIP + account to the ministry; CZ sends only DIČ and compares locally) and by warning that 'not registered' is a hint, not a judgement. It does not explicitly name an alternative tool or state when not to use it, so it falls short of the top score.

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