Geo-Parity

How far a monthly pension goes, country by country

retire_on_budget

Read-onlyIdempotent

Does a fixed monthly pension cover a month of local essentials. Given amount and currency (default GBP 1,500), returns every spine country ranked by coverage — the pension in USD divided by the country's MODELLED monthly essentials (the site's price basket scaled by the PPP price level, checked against real series and wrong both ways) — with the essentials figure, healthcare out-of-pocket per person per month (World Bank / WHO), life expectancy (World Bank) and the kind of retiree visa the country offers beside each row. Coverage is an ordering, not a budget; the pension is taken as fixed at the site's FX snapshot. Different from pension_abroad, which re-prices a pension against the origin's price level to say what it is worth relative to home. Published rules and modelled figures on the dates shown, for information only — entitlements depend on a person's record and consulates decide; every response says so first.

Input Schema

Name	Required	Description	Default
`limit`	No	Return at most this many countries.
`amount`	No	Monthly pension, in `currency`.
`currency`	No	ISO 4217 code of `amount`.	GBP

Output Schema

Name	Required	Description	Default
`ok`	No
`rows`	No
`caveats`	No
`pension`	No
`attribution`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

addedInput schema / examples

Added value: +[
+  {
+    "amount": 1500,
+    "currency": "GBP"
+  }
+]

AddedSep 5, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description goes far beyond them: it discloses the ranking methodology, the modelled/published data sources (PPP basket, World Bank/WHO), that coverage is an ordering not a budget, that FX is fixed at the site's snapshot, and that the response leads with a disclaimer. Auth, provenance and limits are all surfaced.

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?

Purpose is front-loaded, but the body is a single dense sentence studded with parentheticals and editorial asides ('wrong both ways', 'checked against real series') that inflate length. It is information-rich but not tight.

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 structure need not be spelled out, yet the description still names the returned fields (essentials figure, out-of-pocket healthcare, life expectancy, retiree visa kind) and the caveats. Complete enough for a complex modelling tool, with only the `limit` behaviour left implicit.

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% and the description reinforces `amount`/`currency` defaults, but it never mentions the `limit` parameter — and its claim to return 'every spine country' sits somewhat awkwardly against a limit parameter. Baseline 3 applies when the schema already carries parameter semantics.

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 computation on a specific resource: given a monthly pension, return spine countries ranked by how far it covers modelled local essentials. It explicitly contrasts itself with `pension_abroad`, so an agent can separate 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 Guidelines4/5

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

Names the alternative (`pension_abroad`) and the condition that selects it — that tool re-prices against the origin's price level, this one ranks abroad coverage. It gives clear context but no explicit when-not-to-use or prerequisite beyond the disclaimer.

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?