Geo-Parity

Check tax-residency risk for remote work abroad

check_tax_residency_risk

Read-onlyIdempotent

Remote Worker Tax Trap radar: evaluates how close a stay is to triggering tax residency (183-day rule with per-country variations across 43 tax jurisdictions) and estimates the tax owed on the FULL annual income if the threshold is crossed — comparing the standard resident effective rate against the country's special expat/nomad regime (Spain's Beckham Law 24%, Portugal's IFICI 20%, Italy's impatriati, territorial/remittance systems, …). Optionally computes leave-by/residency dates from an arrival date and warns where the Schengen 90/180 tourist limit bites first. Early-warning estimates — not tax advice.

Input Schema

TableJSON Schema

Name	Required	Description
`days`	Yes	Days of presence in the relevant counting period.
`income`	Yes	Gross annual income (USD) the residency cliff would expose.
`arrival`	No	Optional arrival date — adds leaveBy and residencyDate to the response.
`country`	Yes	ISO 3166-1 alpha-2 country code (case-insensitive).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`risk`	No
`dates`	No
`projection`	No
`daysRemaining`	No
`thresholdDays`	No
`pctOfThreshold`	No
`schengenWarning`	No

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses that this is an estimation tool, explicitly disclaims tax advice, mentions per-country variation across 43 jurisdictions, and explains optional Schengen-warning behavior. This gives the agent a clear model of what the tool will and will not reliably provide.

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 information-dense but not bloated; it front-loads the core purpose and then details optional behavior and caveats. The list of example regimes adds credibility but is slightly more detailed than strictly necessary, keeping it from a perfect score.

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?

Given the output schema exists, the description does not need to explain return values. It covers purpose, inputs, optional behavior, jurisdictional scope, and a clear not-tax-advice disclaimer, making the tool adequately specified for correct invocation.

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%, and the schema already documents country, days, income, and arrival. The description adds useful context by tying 'arrival date' to leave-by/residency dates and income to the residency cliff, but it does not substantially extend the parameter meaning beyond the schema.

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 description names specific actions — evaluating proximity to tax-residency triggers, estimating tax owed on full annual income, comparing standard vs expat/nomad regimes, and optionally computing leave-by/residency dates. This clearly differentiates it from sibling tools like check_residency or check_schengen by emphasizing tax liability and regime comparison, not just presence rules.

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 description establishes a clear use case: remote workers abroad needing an early-warning tax-residency risk assessment, including tax exposure if a threshold is crossed. It does not explicitly state when to prefer an alternative tool, but the context is specific enough that an agent can infer appropriate usage.

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?