finwire.pl - Polish financial data

Average ZUS pension and benefits

get_pension_stats

Read-onlyIdempotent

Average old-age pension paid by ZUS (gross and net), disability and survivor pensions, number of pensioners, sickness and maternity allowances, the pension to wage ratio finwire_pension_wage_ratio, CPI, minimum pension and indexations, monthly from preliminary ZUS data (without KRUS and uniformed services).

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

Input Schema

Name	Required	Description	Default
`history`	No	Number of past months in the summary, default 12.

Output Schema

Name	Required	Description	Default
`url`	Yes
`asOf`	No
`data`	No
`title`	Yes
`source`	Yes
`docsUrl`	Yes
`license`	Yes
`summary`	Yes
`citation`	Yes
`datasetId`	Yes
`sourceUrl`	No
`truncated`	No
`serverDate`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world, so safety is fully covered. The description adds genuinely useful provenance caveats beyond that: the data is preliminary, monthly, and excludes KRUS and uniformed services. It stops there, saying nothing about revisions, units, or retrieval limits.

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?

One compact, front-loaded sentence that puts the headline series (average old-age pension) first and trails the caveats and ratio identifier. It is a dense run-on list rather than structured prose, but no sentence is wasted.

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 one optional parameter at 100% schema coverage, an output schema covering return values, and annotations covering the safety profile, the only thing left for the description is what data is included and excluded - which it supplies (preliminary ZUS figures, no KRUS or uniformed services). Nothing an agent needs in order to call it correctly is missing.

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?

The single optional 'history' parameter is fully documented in the schema (0-60, default 12), so the 100% coverage baseline of 3 applies. The description's 'monthly' wording hints at the series granularity but adds no syntax or semantics about the history window.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates the specific resource contents very concretely (old-age, disability and survivor pensions, pensioners count, sickness/maternity allowances, wage ratio, CPI, minimum pension and indexations), so an agent knows exactly what dataset it retrieves. However, it never states the operation explicitly (no 'returns'/'fetches'), and it does not distinguish itself from siblings like get_macro_indicator or get_finwire_index.

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

Usage Guidelines2/5

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

There is no statement of when to use this instead of alternatives such as get_macro_indicator or get_finwire_index, and no prerequisites. The only guidance-like content is scope framing ('monthly from preliminary ZUS data (without KRUS and uniformed services)'), which is coverage info rather than usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All finwire.pl - Polish financial data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.