Skip to main content
Glama

Tax in the year you move between two countries

cross_border_year
Read-onlyIdempotent

Estimates the employment income tax in BOTH countries for the tax year in which someone moves from one country to another: residency status in each country by its own rules (India's 182-day financial-year test, US substantial presence and dual-status, UK split year, Dutch migration year, German part-year liability), the income each country taxes, tax before and after relief for tax paid abroad, social contributions, the combined total in euros and a comparison with staying. Covers 19 countries; each country is taxed for its own tax year containing the move date. Returns what is not covered, assumptions, and for researched corridors (India with the Netherlands, US, UK or Germany; Netherlands with Germany or the UK) the forms and deadlines, treaty notes and official sources. Salaries are full-year rates in each country's own currency.

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": {
      "country_from": "<country_from>",
      "country_to": "<country_to>",
      "move_date": "<move_date>",
      "salary_before_move": "<salary_before_move>",
      "salary_after_move": "<salary_after_move>"
    },
    "name": "cross_border_year"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoAge (16 to 100), default 35
marriedNo
childrenNoNumber of children (0 to 10)
move_dateYesFirst day living in the new country, YYYY-MM-DD
country_toYesCountry you move to (ISO code)
india_rnorNoIndia: not ordinarily resident (non-resident 9 of the last 10 years, or 729 days or fewer in India in 7 years)
country_fromYesCountry you leave (ISO code)
detail_afterNoOptional tax details for the country you move to, as on its net pay page: married, spouse_income, children, age, pension_pct, bonus (yearly, extra) and options (the country's own options by key, see tax_rules_covered)
return_afterNoOptional full tax return arguments for the country you move to: the same arguments as that country's income tax return tool. Its salary and part-year residence are filled in from the dates; everything else is yours.
detail_beforeNoOptional tax details for the country you leave, as on its net pay page: married, spouse_income, children, age, pension_pct, bonus (yearly, extra) and options (the country's own options by key, see tax_rules_covered)
return_beforeNoOptional full tax return arguments for the country you leave: the same arguments as that country's income tax return tool. Its salary and part-year residence are filled in from the dates; everything else is yours.
uk_split_yearNoUnited Kingdom: treat the UK part of the year as resident (split-year treatment); default true
indian_citizenNoIndia: you are an Indian citizen (default true)
home_after_moveNoWhere your home and family are after the move; decides the treaty tie-breaker (default new_country; none applies no tie-breaker)
salary_after_moveYesYearly salary rate in the country you move to, in its currency
us_days_last_yearNoDays spent in the US last year (substantial presence test)
salary_before_moveYesYearly salary rate in the country you leave, in its currency
us_days_year_beforeNoDays spent in the US the year before last
nl_30_percent_rulingNoNetherlands: the 30% ruling applies
us_citizen_or_green_cardNoUnited States: citizen or green card holder

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / country_from / enum
      Previous value: -[
      -  "BE",
      -  "BG",
      -  "CN",
      -  "DE",
      -  "ES",
      -  "FR",
      -  "GB",
      -  "GR",
      -  "ID",
      -  "IN",
      -  "IT",
      -  "MA",
      -  "NL",
      -  "PL",
      -  "RO",
      -  "TR",
      -  "US"
      -]New value: +[
      +  "AE",
      +  "BE",
      +  "BG",
      +  "CN",
      +  "DE",
      +  "ES",
      +  "FR",
      +  "GB",
      +  "GR",
      +  "ID",
      +  "IN",
      +  "IT",
      +  "MA",
      +  "NL",
      +  "PL",
      +  "RO",
      +  "SG",
      +  "TR",
      +  "US"
      +]
    • changedInput schema / properties / country_to / enum
      Previous value: -[
      -  "BE",
      -  "BG",
      -  "CN",
      -  "DE",
      -  "ES",
      -  "FR",
      -  "GB",
      -  "GR",
      -  "ID",
      -  "IN",
      -  "IT",
      -  "MA",
      -  "NL",
      -  "PL",
      -  "RO",
      -  "TR",
      -  "US"
      -]New value: +[
      +  "AE",
      +  "BE",
      +  "BG",
      +  "CN",
      +  "DE",
      +  "ES",
      +  "FR",
      +  "GB",
      +  "GR",
      +  "ID",
      +  "IN",
      +  "IT",
      +  "MA",
      +  "NL",
      +  "PL",
      +  "RO",
      +  "SG",
      +  "TR",
      +  "US"
      +]
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare it as a safe, idempotent, closed-world read; the description goes well beyond that by disclosing coverage limits (19 countries), the per-country tax-year convention, that uncovered items and assumptions are returned, that researched corridors add forms, deadlines, treaty notes and sources, and that salaries are full-year rates in local currency. With no output schema, this description carries the return-value burden and does so well.

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?

Purpose and scope are front-loaded in the opening clause, and no sentence is filler. The first sentence is a long, heavily comma-laden enumeration of national residency rules, which is dense but each element (India 182-day, US substantial presence, UK split year, etc.) conveys distinct capability.

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 a 20-parameter tool with nested detail/return objects and no output schema, the description covers coverage, output contents, corridor depth and currency conventions. The remaining gap is how income is apportioned between the two countries across differing tax years — that mechanism is left implicit even though it drives the result.

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 already 95%, so the schema documents nearly all 20 parameters, including enums and nested objects; that sets the baseline at 3. The description adds one genuinely useful clarification — salaries are full-year rates in each country's own currency, which prevents a proration mistake — and explains that return_before/return_after inherit salary and part-year residence from the dates. That is helpful but thin relative to the parameter surface.

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 ('estimates') and a precise resource ('employment income tax in BOTH countries for the tax year in which someone moves'), plus the exact scope (move year, both countries, relief for foreign tax). This is clearly distinguishable from the single-country siblings such as income_tax_return_netherlands or united_states_income_tax_return.

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 trigger condition is unambiguous: use it for the year of a cross-border move, not for a normal single-country year. It also points to the per-country return tools indirectly via return_before/return_after ('the same arguments as that country's income tax return tool'). It stops short of an explicit 'use X instead when...' routing statement, so it earns a 4 rather than a 5.

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