Skip to main content
Glama

Mirabello Immigration Intelligence

Find Retirement & Passive-Income Residence

find_retirement_routes
Read-onlyIdempotent

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.

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": "find_retirement_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results returned (default 5, up to 62). The list is ranked; total_matched gives the full count.
regionNoRegion filter, case-insensitive: e.g. "Latin America", "Caribbean", "Europe", "Asia", "Middle East", "Americas".
min_scoreNoOnly routes with a Golden Retirement score at or above this value (0 to 100); unscored routes are excluded. Results are then ordered by score.
dependantsNoNumber of dependants (spouse, children) to include; routes with a per-dependant income add-on raise the requirement accordingly. Default 0.
golden_onlyNotrue = only routes rated Golden by the Mirabello Golden Retirement Index; results are then ordered by score. Default false.
income_typeNoWhat the income is: pension (state or private retirement pension), passive (rents, dividends, interest), or either/both. Default either.
net_worth_usdNoLiquid savings or investable net worth in USD, for routes that accept a deposit, savings balance or assets instead of income. Optional.
monthly_income_usdNoYour regular monthly income in USD (pension and/or passive income). Optional; without it qualification by income is left open.
max_stay_days_per_yearNoThe 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_onlyNotrue = only routes where foreign income is untaxed for a tax resident (exempt, territorial or remittance basis). Default false.

Output Schema

NameRequiredDescriptionDefault
errorNo
termsNo
sourceNo
book_urlNo
providerNo
disclaimerNo
data_updatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Maximum results returned (default 5, up to 62). The list is ranked; total_matched gives the full count.",
      +  "examples": [
      +    5
      +  ],
      +  "maximum": 62,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedOutput schema / description
      Previous value: -"Mirabello response envelope. Tool-specific fields vary; the provenance/disclaimer envelope is always present."New value: +"Mirabello envelope; tool fields vary; error only on failure."
    • removedOutput schema / properties / book_url / description
      Removed value: -"Link to request a consultation with a Mirabello specialist, for a personal case."
    • removedOutput schema / properties / data_updated / description
      Removed value: -"Date the underlying dataset was last updated."
    • removedOutput schema / properties / disclaimer / description
      Removed value: -"Information, not legal/tax/financial/immigration advice; figures indicative."
    • removedOutput schema / properties / error / description
      Removed value: -"Present only when the request could not be fulfilled."
    • removedOutput schema / properties / provider / description
      Removed value: -"Always \"Mirabello Consultancy\"."
    • removedOutput schema / properties / source / description
      Removed value: -"Attribution for the data, when it is not Mirabello Consultancy itself."
    • removedOutput schema / properties / terms / description
      Removed value: -"Acceptable-use and information-not-advice terms."
  2. Changed2 schema fields changed
    • 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"
      +}
  3. Added

TDQS

A4/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 safety is covered; the description adds real behavioral context beyond that: qualification is 'indicative' with FX assumptions, unverified figures are withheld rather than estimated, tax labels for specific countries are surfaced, and it disclaims 'Information, not advice.' No pagination or ranking-mechanics detail is given beyond what the schema says.

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 description is front-loaded with the core purpose and the qualifying criterion, and every clause carries filtering or return-value information. It is dense and somewhat run-on as a single block, but there is little true filler.

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 10-parameter, zero-required, read-only search tool with an output schema and full annotations, the description supplies everything an agent needs: scope, filter semantics, score/golden behavior, and the shape of each returned route, plus data-integrity caveats.

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%, so every parameter is already documented in the schema. The description restates the filter set (income, net worth, stay days, region, dependants, untaxed income) and explains golden_only/min_score semantics, but that largely duplicates the schema's own descriptions; it adds little beyond the structured fields.

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 states a specific verb (find) and resource (retirement/passive-income residence routes), and narrows the scope decisively with 'qualify on income or savings, not an investment,' which separates it from investment-style programme tools. It does not name a specific sibling to route away to (e.g. find_pathways), so it falls short of the 5 bar.

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?

The exclusion criterion ('not an investment') gives clear selection context, and the listed filters imply when the tool is appropriate. However, there is no explicit 'use X instead when...' routing to a named alternative among the many sibling find_* and get_programme tools.

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.