Geo-Parity

Rank countries by quality of life vs cost

rank_livability

Read-onlyIdempotent

Quality-of-Life vs Cost matrix: ranks 41 countries by a user-weighted composite of livability metrics (median broadband Mbps, safety, healthcare, air quality, English usability — curated country-level data replacing the discontinued Teleport API) against the monthly cost of single-person essentials at local purchasing-power prices. Returns per-country composite and value scores, lifestyle label for your budget (comfortable → like royalty), nomad-visa eligibility, and days-to-tax-residency. Curated estimates — verify locally.

Input Schema

Name	Required	Description
`budget`	No	Monthly budget (USD) — drives lifestyle labels and visa eligibility.
`weights`	No	Five comma-separated 0–10 weights: internet,safety,healthcare,air,english (default 5,5,5,5,5).
`maxBudget`	No	Filter: keep countries whose monthly essentials cost ≤ this (USD).
`minSafety`	No	Filter: minimum safety score, 0–100.
`minInternet`	No	Filter: minimum median broadband, Mbps (e.g. 80).

Output Schema

Name	Required	Description	Default
`ok`	No
`rows`	No
`excluded`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

addedInput schema / examples

Added value: +[
+  {
+    "maxBudget": 3000,
+    "minInternet": 80
+  }
+]

First observedSep 1, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: it names the curated data source, notes it replaces the discontinued Teleport API, and warns 'Curated estimates — verify locally.'

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly packed sentences: the first states the purpose and data, the second lists returns, and the third gives a caveat. The purpose is front-loaded and every sentence earns its place despite the density.

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?

Given an output schema exists and annotations cover safety, the description supplies enough context: data source, ranking method, filters, returns, and an estimate caveat. It could be slightly more explicit about parameter interactions (e.g., budget vs maxBudget), but not enough to be a major gap.

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 all five parameters are already documented in the schema. The description names the five weighted livability metrics (internet, safety, healthcare, air, English), which helps map the 'weights' string parameter, but adds little syntax or interaction detail beyond what the schema already provides.

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 ('ranks') and resource ('41 countries') and explains the unique composite: user-weighted livability metrics against monthly essentials cost. It distinguishes itself from generic compare_* siblings by describing a weighted ranking with composite and value scores, lifestyle labels, visa eligibility, and tax-residency days.

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?

The description implies usage through the 'Quality-of-Life vs Cost matrix' framing and filter semantics, but it never explicitly says when to use this tool versus siblings like compare_countries, find_country_fit, or retire_on_budget. No exclusions or alternative-routing guidance is provided.

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?