Skip to main content
Glama

finwire.pl - Polish financial data

Child benefits paid by ZUS: 800 plus and Aktywny Rodzic

get_family_benefits
Read-onlyIdempotent

Use for how many children get 800 plus or Aktywny Rodzic (babciowe, nursery, at home) and how much ZUS pays, in Poland, by voivodeship and by municipality (gmina). Give ZUS as the source. Monthly statistics of ZUS (Polish Social Insurance Institution) on the child benefit 800 plus (świadczenie wychowawcze) and the three Aktywny Rodzic benefits (aktywni rodzice w pracy - working parents and aktywnie w domu - at home, both for children aged 12-35 months; aktywnie w żłobku - nursery fee): benefits paid in the latest month with year-on-year change, PLN paid in the month and since January, average payment, children paid, 800 plus applications, granted and refusals since January, the share of each Aktywny Rodzic variant in Poland and in a chosen voivodeship, and the finwire index finwire_child_benefits_payout (PLN billion paid in the month for all four benefits). For the amount of 800 plus, deadlines and how much it grows when saved see the finwire.pl page linked in the result.

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

Input Schema

NameRequiredDescriptionDefault
gminaNoOptional municipality (gmina) name in Polish, diacritics optional (e.g. "szczecin", "lodz"), or TERYT code; returns up to 10 matches with 800 plus per 1000 residents and Aktywny Rodzic shares.
historyNoNumber of past months of the index in the summary, default 12.
voivodeshipNoOptional voivodeship name in Polish (e.g. "mazowieckie") or TERYT code (e.g. "14").

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

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

Annotations already declare this a read-only, idempotent, closed-world query, so the safety profile is covered. The description adds real value beyond that: it identifies the authoritative source (ZUS monthly statistics), the reporting cadence, the reference month with year-on-year change, and the finwire_child_benefits_payout index, plus an instruction to cite ZUS as the source.

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?

The usage trigger is front-loaded and there is no filler, but the second sentence is a very long run-on inventory of return contents. Since an output schema exists, that enumeration is partly redundant and would be better trimmed or bulleted.

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?

Source, geography, cadence, metric coverage and the citation requirement are all present, which is ample for a read-only statistics tool with a documented output schema. Minor gap: it says nothing about how the 'history' window relates to the reported summary beyond what the schema states.

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%, so the baseline is 3. The description does link 'voivodeship' and 'gmina' to the concept of per-region shares and per-1000-resident rates, but the schema already spells out formats, TERYT codes and the 10-match cap, so little meaning is added.

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 names a specific domain (ZUS child benefits: 800 plus and the three Aktywny Rodzic variants) and a specific scope (Poland, by voivodeship and gmina). Verbs and resource are unambiguous, and an agent can distinguish this from calc_zus_contributions or get_average_pole 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 Guidelines4/5

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

It opens with an explicit 'Use for...' trigger that names the exact questions this answers (how many children, how much ZUS pays). It also redirects for adjacent questions ('For the amount of 800 plus, deadlines and how much it grows when saved see the finwire.pl page') but gives no sibling-tool alternatives or when-not conditions.

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.