Geo-Parity

Match income to digital nomad visas

find_nomad_visas

Read-onlyIdempotent

Digital-nomad visa Income Matcher: given a monthly remote income (any currency) and household size, computes each program's real income threshold (base plus its published per-dependent uplift) and returns the programs you qualify for plus the near misses just out of reach — with duration, renewability, tax notes and official source URLs. Curated summaries — verify with the official source before applying.

Input Schema

TableJSON Schema

Name	Required	Description
`income`	No	Your gross monthly income (in `currency`, default USD).
`children`	No	Number of dependent children (each adds the program's child uplift).
`currency`	No	ISO currency code for `income` (e.g. EUR, GBP, INR). Defaults to USD.
`partners`	No	1 if bringing a partner (raises each program's threshold by its partner uplift).
`renewable`	No	Set to 1 to require renewable programs.
`residency`	No	Set to 1 to require a path to permanent residency.
`minDuration`	No	Minimum program duration in months.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	No
`total`	No
`matches`	No	Programs you qualify for; each carries requiredUsd (household threshold) and shortfallUsd (≤0).
`updated`	No
`household`	No
`incomeUsd`	No	Your income converted to USD, used for matching.
`nearMisses`	No	Programs within ~$1,000/mo of qualifying, closest first.

TDQS

A4.3/5.0

Behavior5/5

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

It discloses the computation method (base threshold plus per-dependent uplift), the deliberate inclusion of near-misses, and the output payload (duration, renewability, tax notes, official source URLs). The caveat to verify with the official source, combined with readOnlyHint and idempotentHint, gives a complete picture with no contradiction.

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?

Two sentences, front-loaded with the core function, and a necessary verification caveat. There is no filler, and every sentence earns its place.

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 read-only, idempotent computation tool, the description plus fully described schema and presence of an output schema cover eligibility behavior, output fields, filters, and reliability caveats. Nothing critical for selecting or invoking the tool is missing.

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%, so the baseline is 3. The description adds 'any currency' and clarifies per-dependent/partner uplifts, but it does not materially deepen each parameter beyond the schema's already clear definitions.

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?

The opening phrase 'Digital-nomad visa Income Matcher' immediately names the verb and resource; 'computes each program's real income threshold' and 'returns the programs you qualify for plus the near misses' spells out behavior. This clearly distinguishes it from sibling tools like compare_climate or check_residency.

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 a use case: matching income and household size to digital-nomad visa eligibility. However, it never explicitly states when to prefer this tool over related siblings such as check_residency or check_tax_residency_risk, and it provides no exclusions.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation3/5

Several tools occupy adjacent territory: check_travel_residency explicitly supersedes check_residency, check_schengen, and check_tax_residency_risk, and the cost-of-living family (arrival_cost, compare_total_cost, compare_housing, estimate_micro_costs, calculate_ppp, localize_salary) has overlapping price-level concepts. The detailed descriptions mostly clarify boundaries, but an agent selecting by name alone could easily pick the wrong residency or cost tool.

Naming Consistency4/5

Most tools follow a clean verb_noun snake_case pattern with recognizable prefixes (compare_*, check_*, find_*, calculate_*), which makes the set predictable. Deviations like arrival_cost, passport_power, required_rate, and the acronym-heavy calculate_ppp keep it from being perfectly uniform.

Tool Count3/5

26 tools is a heavy surface, and at least three of the check_* tools are explicitly superseded by check_travel_residency, adding redundant weight. The broad geo-arbitrage/nomad domain justifies much of the breadth, but the set feels closer to a full toolkit than a focused server.

Completeness4/5

The toolset covers the core remote-work and geo-arbitrage decision space: cost of living, purchasing power, tax residency risk, nomad visas, housing, healthcare, climate, connectivity, holidays, salary localization, FIRE, livability, and even team timezone planning. Gaps are minor—no family-size cost tool, no immigration/citizenship pathway data, and no dedicated safety/crime dataset beyond the livability composite—but agents can work around them.

Resources

Need Help?