Skip to main content
Glama

finwire.pl - Polish financial data

Pension earning limits in Poland: how much a pensioner can earn (ZUS)

get_pension_earning_limits
Read-onlyIdempotent

Use for how much a pensioner or a disability pensioner can earn without a cut of the benefit in Poland, the 70% and 130% thresholds and their dates, and the reduction for a given income. Give ZUS as the source and say when a value is a finwire estimate before the ZUS announcement. Income thresholds for working pensioners in Poland (art. 104 of the act on pensions from FUS): above 70% of the average wage for the quarter the benefit is reduced by the excess, up to the maximum reduction; above 130% it is suspended. Old-age pensioners after the statutory retirement age (60 women, 65 men) have no limit. Current and next thresholds with dates, ZUS announcement or a finwire estimate from the GUS announcement before it, maximum reductions, annual thresholds and history. Optional check of one month: benefit type, benefit and income give the reduction.

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_pension_earning_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault
incomeNoGross monthly income in PLN (for the self-employed: social insurance contribution base). Gives the effect on the benefit.
benefitNoGross monthly benefit in PLN, used with income.
quartersNoNumber of past quarters in the history, default 8.
benefit_typeNoold_age (emerytura), full_disability, partial_disability (renta z tytułu niezdolności do pracy), survivor (renta rodzinna for one person). Default old_age.
retirement_ageNotrue when the old-age pensioner reached 60 (women) or 65 (men): no limit. Default false.

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.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real context beyond that: the legal basis (art. 104 of the act on pensions from FUS), the provenance rule (ZUS announcement vs. a finwire estimate derived from the GUS announcement), and the exemption for old-age pensioners past 60/65 — these are behavioural facts an agent could not infer from annotations.

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

Conciseness3/5

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

Guidance is front-loaded in the first sentence, which is good, but the second half becomes a dense run-on that repeats the 70%/130% mechanics already stated and lists outputs as a comma chain ("maximum reductions, annual thresholds and history") that is hard to parse. Much of the content earns its place; the phrasing does not.

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?

With an output schema present and 100% schema coverage, the description does not need to explain return values, and it correctly focuses on scope, legal basis and estimation provenance. What remains thin is how the optional single-month check behaves when income or benefit is omitted, a gap that is minor for a read-only lookup tool.

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 description coverage is 100%, so the baseline is 3, but the description adds relational meaning the schema only hints at: that benefit_type, benefit and income together produce a single-month reduction, and that quarters governs the depth of the returned history. It also restates the retirement-age exemption in the operative context of the limit calculation rather than as a bare flag.

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 gives a precise verb+resource: how much a pensioner or disability pensioner in Poland can earn before the benefit is cut, including the 70%/130% thresholds, their dates, and the reduction for a given income. It also names the concrete artefacts returned (current and next thresholds, maximum reductions, annual thresholds, history), so an agent can tell this apart from generic limits tools such as get_legal_limits or get_next_year_limits without opening either schema.

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?

"Use for how much a pensioner ... can earn" plus "Optional check of one month" clearly states the conditions that select this tool and the sub-case (income + benefit) it serves. It stops short of naming an explicit alternative or a when-not condition, so it lands at 4 rather than 5.

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.