Skip to main content
Glama

finwire.pl - Polish financial data

PIT settlement in Poland by tax year (Ministry of Finance)

get_pit_settlement_stats
Read-onlyIdempotent

Use for how many people in Poland settle PIT, how many are in the second tax bracket and what share of tax they pay, how many use child relief, IKZE or other reliefs, overpayments, flat tax and lump-sum tax returns. For PIT by municipality, use get_regional_data. For tax rates and limits, use get_legal_limits. National statistics of the annual PIT settlement from the yearly Ministry of Finance information (every tax year since 2019): taxpayers on the tax scale, returns by form (PIT-36, PIT-36L, PIT-37, PIT-38, PIT-39, PIT-28 lump-sum), taxpayers in the first and second bracket with the threshold and the second bracket share in tax due, reliefs deducted from income (IKZE, thermal modernisation, internet, rehabilitation, donations, trade union dues) with taxpayers, amount and average, child relief (taxpayers, children, amount), overpayments in returns, flat tax, capital gains and crypto income, and the finwire index finwire_pit_top_bracket_multiplier. Optional year selects one tax year. For PIT by municipality use get_regional_data; for tax rates and limits use get_legal_limits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_pit_settlement_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoTax year; default the latest published.

Output Schema

NameRequiredDescriptionDefault
urlYes
asOfNo
dataNo
titleYes
sourceYes
docsUrlYes
licenseYes
summaryYes
citationYes
datasetIdYes
sourceUrlNo
truncatedNo
serverDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuinely useful context beyond that: the data source (yearly Ministry of Finance information), the temporal coverage (every tax year since 2019), and the specific breakdowns included, including an obscure derived index. It doesn't discuss output shape, but an output schema exists.

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

Conciseness2/5

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

The purpose and sibling routing are front-loaded, which is good, but the body is one bloated paragraph that enumerates every form code and relief type, and the 'For PIT by municipality... for tax rates and limits' sentence appears twice. Substantial trimming would preserve all decision-relevant information.

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 single-optional-parameter statistics tool with an output schema, the description covers source, temporal scope, and metric inventory thoroughly. The redundancy is a style problem rather than a completeness gap, and return-value details are correctly left to the output schema.

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% and the single 'year' parameter already documents its range and 'default the latest published' behavior. The description only restates 'Optional year selects one tax year', adding the implicit 2019 floor already visible in the schema, so the 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?

The opening sentence names a specific verb-and-resource pair ('how many people in Poland settle PIT', bracket shares, reliefs) and enumerates the exact metrics available, so an agent knows precisely what this returns. It also names two siblings (get_regional_data, get_legal_limits) and what they cover instead, making disambiguation immediate.

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

Usage Guidelines5/5

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

It explicitly states when to use this tool ('Use for how many people...') and routes two adjacent needs to named alternatives: municipality-level PIT to get_regional_data and rates/limits to get_legal_limits. The only weakness is that this routing sentence is repeated verbatim at the end, which is wasteful rather than misleading.

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.