Skip to main content
Glama

finwire.pl - Polish financial data

Average pension: ZUS vs KRUS

get_pension_systems
Read-onlyIdempotent

Use to compare the average ZUS pension with the average KRUS farmer pension, by year and province. For the latest monthly ZUS pension, use get_pension_stats. Average monthly gross old-age pension from ZUS and average pension and disability benefit of farmers from KRUS (GUS BDL; KRUS figure covers both): yearly since 1999 for Poland and 16 provinces, the latest year-to-date period with the previous year, gap in PLN and KRUS as % of ZUS. For the latest monthly ZUS pension, use get_pension_stats.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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

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

Annotations already declare readOnly/idempotent/non-destructive/non-open-world, so safety is covered. The description adds genuinely non-obvious context: data sources (GUS BDL), the caveat that the KRUS figure covers both pension and disability benefit, historical depth since 1999, and the YTD-plus-previous-year convention. It stops short of noting refresh cadence or any known data caveats beyond the KRUS aggregation note.

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 sentence "For the latest monthly ZUS pension, use get_pension_stats" appears verbatim twice, once at the start and once at the end, which is pure duplication. The middle sentence is dense but every clause carries real information about sources and output composition.

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 zero-parameter tool with an output schema and full annotations, the definition covers source, coverage period, geography, and the compared metrics, which is enough to call it correctly. The only real defect is structural redundancy rather than missing information.

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?

The tool takes zero parameters, so there is no parameter semantics to add; the baseline for a 0-param tool applies. The description instead clarifies the fixed scope (Poland plus 16 provinces, yearly since 1999) that an agent would otherwise have to guess.

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?

Opens with a specific verb and resource: "compare the average ZUS pension with the average KRUS farmer pension, by year and province." It also names the contrast case (monthly ZUS pension) and routes it to get_pension_stats, so an agent can distinguish the two 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 Guidelines5/5

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

Explicitly states when to use this tool (yearly/provincial ZUS vs KRUS comparison) and names the alternative for a different need: "For the latest monthly ZUS pension, use get_pension_stats." The condition that selects the sibling is concrete, not inferred.

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.