Skip to main content
Glama

Where to live: rank 100 places on your profile

rank_places
Read-onlyIdempotent

Ranks Patrician.ch's 100 tier one places to live and relocate to (Monaco, Dubai, Zug, Lugano, Miami, Singapore, Lake Como, Lisbon and more, across 47 countries and territories) on one person's or family's income, passports, household, current home and priorities. For each place: effective income tax, net income, what the household keeps over the period, the exit tax charged by the current country, wealth tax, the residence route (including golden visa and investor routes where they exist) and the patrician.ch page. Returns the top 10, a link to the full ranking of all 100 on patrician.ch, and a link to a free preview of a written Private Dossier on the same inputs. Use it for relocation, moving abroad, tax residency and "where should I live" questions from high earners, founders before an exit, and high net worth families.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "annual_income_usd": "<annual_income_usd>"
    },
    "name": "rank_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many places to return, at most 10. Default 10. The full ranking of all 100 is on the site, at full_ranking_url.
yearsNoHorizon in years. Default 10.
childrenNo
householdNosolo, couple, or kids (a family with children).
passportsNoPassports the person holds: eu (any EU country), uk, us, ch, ae, ca, au, sg, jp, il, or other.
prioritiesNoOptional weights from 0 to 10.
current_homeNoWhere the person lives now, as a city (New York, London, Paris, Zurich, Tel Aviv, Dubai, Singapore, Sydney, Munich, Toronto and others) or a country. Sets the exit charge and flight times.
annual_income_usdYesYearly income in US dollars.
employment_incomeNoTreat the income as one person's salary and add the employee's compulsory social contributions where Patrician.ch models them. Default false.
liquidity_event_usdNoA planned company sale or other liquidity event, in US dollars, if any.
investable_assets_usdNoInvestable assets in US dollars, for wealth tax.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no output schema, the description usefully discloses what comes back: per-place effective tax, net income, retained amount, exit tax, wealth tax, residence route, site page, plus the top-10-only truncation with links to the full 100 and a free dossier preview. Annotations already cover safety (readOnly, idempotent, non-destructive, openWorldHint=false), and the fixed 100-place dataset is consistent with a closed-world hint. Rate limits and caching behavior are not stated.

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 and usage are front-loaded, but the parenthetical city list ("Monaco, Dubai, Zug, Lugano, Miami, Singapore, Lake Como, Lisbon and more, across 47 countries and territories") and the long output inventory add marketing-style bulk. The output enumeration earns its place given no output schema; the city roll-call largely does not.

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 an 11-parameter tool with a nested priorities object and no output schema, the description covers the compute model, the delivered fields, and the truncation-plus-links behavior, which is enough to call it correctly. Minor gaps remain around result ordering and whether repeated calls with the same inputs are guaranteed identical.

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 91%, so the schema already documents nearly every parameter including enums and bounds. The description only restates the input categories in prose (income, passports, household, current home, priorities) and adds no format or weighting semantics beyond that, so it is a baseline 3.

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 names a specific verb (ranks), a bounded resource (100 tier-one places to live) and the inputs it ranks on, so the operation is unmistakable. It does not explicitly differentiate itself from siblings like compare_places or place_profile, so it stops short of a 5.

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?

"Use it for relocation, moving abroad, tax residency and 'where should I live' questions from high earners, founders before an exit, and high net worth families" gives a clear use context and audience. There are no explicit when-not-to-use rules or named alternatives, which keeps it out of 5 territory.

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.

Resources