mcp-server

Find Retirement & Passive-Income Residence

find_retirement_routes

Read-only

Find RETIREMENT and PASSIVE-INCOME residence routes (pensionado, rentista, retiree visas) that qualify on income or savings, not an investment. Filter by monthly income in USD, income type, net worth, the most days a year you want to spend there, region, dependants and untaxed foreign income. golden_only returns only routes rated Golden by the Mirabello Golden Retirement Index (score 70+/100: no investment, little or no tax on foreign income, little presence, little renewal); min_score sets a score floor. Each route gives its official requirement in its legal currency, whether you appear to qualify (indicative FX), the stay rule, the foreign-income tax label (Mexico, Portugal, Colombia and Brazil tax the foreign pension of a tax resident), the Golden Retirement score with its reasons, the path to permanent residence, and the official source. Unverified figures are withheld, never estimated. Information, not advice.

Input Schema

TableJSON Schema

Name	Required	Description
`region`	No	Region filter, case-insensitive: e.g. "Latin America", "Caribbean", "Europe", "Asia", "Middle East", "Americas".
`min_score`	No	Only routes with a Golden Retirement score at or above this value (0 to 100); unscored routes are excluded. Results are then ordered by score.
`dependants`	No	Number of dependants (spouse, children) to include; routes with a per-dependant income add-on raise the requirement accordingly. Default 0.
`golden_only`	No	true = only routes rated Golden by the Mirabello Golden Retirement Index; results are then ordered by score. Default false.
`income_type`	No	What the income is: pension (state or private retirement pension), passive (rents, dividends, interest), or either/both. Default either.
`net_worth_usd`	No	Liquid savings or investable net worth in USD, for routes that accept a deposit, savings balance or assets instead of income. Optional.
`monthly_income_usd`	No	Your regular monthly income in USD (pension and/or passive income). Optional; without it qualification by income is left open.
`max_stay_days_per_year`	No	The most days a year you are willing to spend in the country. Routes with a higher stated minimum are excluded; routes whose stay rule is not stated are kept and flagged.
`foreign_income_untaxed_only`	No	true = only routes where foreign income is untaxed for a tax resident (exempt, territorial or remittance basis). Default false.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present only when the request could not be fulfilled.
`terms`	No	Acceptable-use and information-not-advice terms.
`source`	No	Attribution for the data, when it is not Mirabello Consultancy itself.
`book_url`	No	Link to request a consultation with a Mirabello specialist, for a personal case.
`provider`	No	Always "Mirabello Consultancy".
`disclaimer`	No	Information, not legal/tax/financial/immigration advice; figures indicative.
`data_updated`	No	Date the underlying dataset was last updated.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 11, 2026

addedInput schema / properties / golden_only

Added value: +{
+  "description": "true = only routes rated Golden by the Mirabello Golden Retirement Index; results are then ordered by score. Default false.",
+  "type": "boolean"
+}

addedInput schema / properties / min_score

Added value: +{
+  "description": "Only routes with a Golden Retirement score at or above this value (0 to 100); unscored routes are excluded. Results are then ordered by score.",
+  "type": "number"
+}

AddedOct 8, 2026

TDQS

A4.1/5.0

Behavior5/5

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

With readOnlyHint and destructiveHint=false already covering safety, the description adds substantial behavioral context: what each route returns (official requirement in legal currency, stay rule, tax label, Golden score with reasons, permanent-residence path, source), the key caveat that unverified figures are withheld rather than estimated, and the FX-based indicative qualification. It also names the specific jurisdictions that tax foreign pensions, which an agent cannot infer from schema or annotations.

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?

The purpose and scope are front-loaded in the first sentence, followed by filter summary and then return/behavior detail. It is dense and long, but nearly every clause carries decision-relevant information; only the long parenthetical listing of return fields edges toward over-stuffing.

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?

For a 9-parameter, all-optional, read-only discovery tool with an output schema, the description is complete: it explains the filters' intent, the meaning of Golden/min_score, the data-quality policy, and the returned fields. An agent has everything needed to invoke it correctly and interpret results, and the safety profile is fully covered by annotations.

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 already 100%, setting a baseline of 3, but the description goes further: it defines the 'Golden' rating criterion (score 70+/100, no investment, low foreign-income tax, little presence/renewal) that the schema merely references, and clarifies behavioral nuances like routes with unstated stay rules being kept and flagged, and dependant income add-ons raising requirements.

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 gives a specific verb and resource ('Find RETIREMENT and PASSIVE-INCOME residence routes') and enumerates the real-world programs (pensionado, rentista, retiree visas). It cleanly scopes itself away from investment-based routes ('qualify on income or savings, not an investment'), which implicitly distinguishes it from the many citizenship/programme siblings, though it never names a specific sibling tool.

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

Usage Guidelines3/5

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

Usage is strongly implied by the scope and the enumerated filters, making it obvious this is for income/savings-based retirement residence. However, it never states when NOT to use it or points to an alternative (e.g. recommend_programmes or find_pathways) for users who can invest or want citizenship, so routing advice is left to inference.

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

All mcp-server 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.