Skip to main content
Glama

finwire.pl - Polish financial data

Poland vs OECD countries: pension replacement rates and tax wedge (OECD)

get_oecd_comparison
Read-onlyIdempotent

Use to compare Polish pensions (replacement rate) or labour taxes (tax wedge) with OECD countries, also countries outside the EU such as the United States, the United Kingdom or Japan. For the tax wedge in EU countries, use get_eu_earnings. For a pension forecast by birth year, use get_pension_forecast. OECD comparative data. Pension replacement rates from Pensions at a Glance: first pension as % of individual earnings before retirement, net and gross, men and women, average wage, full career from age 22, mandatory schemes, for Poland, the OECD average and every country of the OECD comparison, with the rank of Poland and finwire_oecd_pension_gap (Poland minus the OECD average, percentage points). Tax wedge from Taxing Wages: income tax plus employee and employer social contributions as % of total labour costs for six household profiles in every OECD country (also outside the EU: United States, United Kingdom, Japan, Canada, Switzerland, Norway), history of Poland and the OECD average since 2000, and finwire_oecd_tax_wedge_gap. For the tax wedge in EU countries from Eurostat use get_eu_earnings. For a pension forecast for a birth cohort use get_pension_forecast.

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

Input Schema

NameRequiredDescriptionDefault
topicNopension (replacement rates) or tax-wedge; default both.
profileNoTax wedge household profile, default single_100 (single person without children, average wage).

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 establish readOnly, idempotent, non-destructive, and closed-world behavior, so the description is not burdened with safety disclosure. It adds genuine context beyond annotations: the underlying sources (Pensions at a Glance, Taxing Wages), the definitions used (first pension as % of individual earnings, full career from age 22, mandatory schemes; income tax plus employee/employer contributions as % of labour costs), the coverage (every OECD country plus Poland's rank), and time depth since 2000. It does not discuss defaults for how 'both' topics are returned, keeping it short of a 5.

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 alternative-tool routing is stated twice in near-identical wording ('For the tax wedge in EU countries, use get_eu_earnings' and 'For the tax wedge in EU countries from Eurostat use get_eu_earnings'; the pension forecast pointer likewise repeats), and the non-EU country list appears twice. The middle is an unstructured run-on that mixes sources, definitions, and output fields; the useful routing sentences should be front-loaded once and the rest compressed.

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 two-optional-parameter read tool with a full output schema, the definition covers coverage scope, data sources, definitions, and alternatives, which is more than enough for correct invocation. Minor gaps remain: it never says how to scope results to Poland alone versus all OECD countries, and it is silent on defaults for the tax-wedge history window.

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 description coverage is 100% and both parameters are enums with documented defaults, so the schema does the heavy lifting and a 3 baseline applies. The description only reinforces that six household profiles exist and that the topic defaults to both; it does not explain individual profile values or how profile interacts with the pension topic.

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 comparison (Polish pension replacement rates and tax wedge versus OECD countries) and enumerates exactly what is produced: replacement rates net/gross by sex, Poland's rank, finwire_oecd_pension_gap, six tax-wedge household profiles, and history since 2000. It also draws a clear boundary against get_eu_earnings and get_pension_forecast, so an agent can separate it from siblings without opening schemas.

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?

Explicit routing is given: use this for OECD comparison data including non-EU countries, use get_eu_earnings for EU tax wedge from Eurostat, and use get_pension_forecast for a pension forecast by birth year. It also states the negative case (don't use this for EU-sourced tax wedge), which is the strongest form of guidance.

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.