Geo-Parity

What a pension is worth abroad, and how fast it erodes

pension_abroad

Read-onlyIdempotent

A fixed pension paid from one country and spent in another, after the exchange rate, the destination's price level and the destination's inflation. Converts amount in currency at the site's FX snapshot, re-prices it at the destination through the PPP engine (the same price-level comparison as calculate_ppp), and projects it flat at the destination's latest annual inflation for years (1-40, default 10), returning what it is worth there today and after the period, in USD and local currency, with the share of purchasing power lost. Without amount, the origin's typical state pension is used — OECD's net replacement rate for an average earner on the modelled median wage — and basis says so; 33 origins have a rate, the rest need amount. Holds the pension and the exchange rate fixed and says so; many state pensions are uprated, and some are frozen for expatriates in particular countries. Not financial advice.

Input Schema

Name	Required	Description
`to`	Yes	Country it will be spent in, ISO alpha-2 (e.g. "PT").
`from`	Yes	Country the pension is paid from, ISO alpha-2 (e.g. "GB").
`years`	No	Years to project (whole number, default 10).
`amount`	No	Monthly pension in `currency`. Omit for the origin's typical state pension.
`currency`	No	ISO 4217 code of `amount` (default USD).

Output Schema

Name	Required	Description	Default
`ok`	No
`to`	No
`from`	No
`years`	No
`caveats`	No
`pension`	No
`erosionPct`	No
`attribution`	No
`inflationPct`	No
`worthTodayUsd`	No
`worthTodayLocal`	No
`worthAfterYearsUsd`	No
`worthAfterYearsLocal`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

addedInput schema / examples

Added value: +[
+  {
+    "amount": 1000,
+    "currency": "GBP",
+    "from": "GB",
+    "to": "PT",
+    "years": 10
+  }
+]

AddedSep 4, 2026

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, so the bar is lower. Beyond that, the description discloses the fixed-pension/fixed-FX modelling assumption, warns that many state pensions are uprated and some are frozen for expatriates, and disclaims financial advice — useful limits an agent otherwise couldn't infer.

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?

Front-loads the core definition well, but the block is dense and long for a 5-parameter tool, with several modelling caveats packed into the middle sentences rather than separated. Informative yet heavier than needed.

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?

An output schema exists so return values needn't be spelled out, yet the description also covers output shape (USD and local, share of purchasing power lost). Combined with defaults, origin coverage and caveats, an agent has enough to call it correctly.

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 coverage is 100% (baseline 3), but the description adds real meaning: `amount` falls back to an OECD net replacement rate available for only 33 origins, `years` is bounded 1-40 default 10, and `basis` reports which path was used. That goes beyond the schema's field-level text.

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?

States a specific verb+resource+scope: a pension paid from one country and spent in another, converted at FX, re-priced via the PPP engine and projected at destination inflation. It explicitly distinguishes itself from calculate_ppp by name and from compare_pension_systems by scope.

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?

Gives clear context for the optional-parameter path: without `amount`, the origin's typical state pension (OECD net replacement rate) is used, 33 origins have a rate and the rest require `amount`. It doesn't explicitly state when to prefer this over siblings like compare_pension_systems or retire_on_budget, but usage conditions are otherwise clear.

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

All Geo-Parity 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.

Resources

Need Help?