Mirabello Immigration Intelligence

Country Tax Profile

get_country_tax

Read-onlyIdempotent

HNWI tax profile for a country (wealth-protection view): personal income tax (worldwide vs territorial), capital gains, inheritance/estate, wealth tax, exit tax, CRS/AEOI status and special regimes (non-dom, lump-sum, NHR/IFICI, flat-tax). For Switzerland also canton and commune tax at standard household profiles (field subnational), for "which canton taxes least" or "Geneva vs Zug". From official/Tier-A sources. Informational only — not tax advice. ISO alpha-2 code or country name.

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": {
      "cc": "<cc>"
    },
    "name": "get_country_tax"
  }
}

Input Schema

Name	Required	Description	Default
`cc`	Yes	ISO alpha-2 country code

Output Schema

Name	Required	Description	Default
`error`	No
`terms`	No
`source`	No
`book_url`	No
`provider`	No
`disclaimer`	No
`data_updated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 25, 2026

changedOutput schema / description

Previous value: -"Mirabello response envelope. Tool-specific fields vary; the provenance/disclaimer envelope is always present."New value: +"Mirabello envelope; tool fields vary; error only on failure."

removedOutput schema / properties / book_url / description

Removed value: -"Link to request a consultation with a Mirabello specialist, for a personal case."

removedOutput schema / properties / data_updated / description

Removed value: -"Date the underlying dataset was last updated."

removedOutput schema / properties / disclaimer / description

Removed value: -"Information, not legal/tax/financial/immigration advice; figures indicative."

removedOutput schema / properties / error / description

Removed value: -"Present only when the request could not be fulfilled."

removedOutput schema / properties / provider / description
```
Removed value: -"Always \"Mirabello Consultancy\"."
```

removedOutput schema / properties / source / description

Removed value: -"Attribution for the data, when it is not Mirabello Consultancy itself."

removedOutput schema / properties / terms / description

Removed value: -"Acceptable-use and information-not-advice terms."

Changed3 schema fields changedOct 8, 2026

removedOutput schema / properties / book_a_consultation

Removed value: -{
-  "description": "URL to book a Mirabello consultation.",
-  "type": "string"
-}

addedOutput schema / properties / book_url

Added value: +{
+  "description": "Link to request a consultation with a Mirabello specialist, for a personal case.",
+  "type": "string"
+}

changedOutput schema / properties / source / description

Previous value: -"Attribution for the data."New value: +"Attribution for the data, when it is not Mirabello Consultancy itself."

Changed1 schema field changedJul 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Mirabello response envelope. Tool-specific fields vary; the provenance/disclaimer envelope is always present.",
+  "properties": {
+    "book_a_consultation": {
+      "description": "URL to book a Mirabello consultation.",
+      "type": "string"
+    },
+    "data_updated": {
+      "description": "Date the underlying dataset was last updated.",
+      "type": "string"
+    },
+    "disclaimer": {
+      "description": "Information, not legal/tax/financial/immigration advice; figures indicative.",
+      "type": "string"
+    },
+    "error": {
+      "description": "Present only when the request could not be fulfilled.",
+      "type": "string"
+    },
+    "provider": {
+      "description": "Always \"Mirabello Consultancy\".",
+      "type": "string"
+    },
+    "source": {
+      "description": "Attribution for the data.",
+      "type": "string"
+    },
+    "terms": {
+      "description": "Acceptable-use and information-not-advice terms.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedJun 27, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already establish readOnly, idempotent, closed-world, non-destructive behavior, so the description doesn't need to. It adds real context — official/Tier-A sourcing and an 'informational only, not tax advice' disclaimer — but says nothing about freshness, coverage gaps, or how the Swiss subnational profiles are scoped/standardized. Solid but not rich.

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?

Front-loaded with the core purpose, then scope, then the Switzerland carve-out and caveat. Dense but largely earned; the parenthetical '(wealth-protection view)' and the long regime acronym list (non-dom, lump-sum, NHR/IFICI, flat-tax) add some clutter.

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?

An output schema exists, so return values needn't be explained; the description still conveys data coverage, source tier, a scope caveat, and the Swiss subnational special case. What's missing is any indication of update recency or known jurisdiction gaps — relevant for a tax-data tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and documents cc as ISO alpha-2 only, yet the description explicitly widens accepted input to 'ISO alpha-2 code or country name' — a meaningful addition the schema would otherwise contradict. It's a single short clause, so no more depth is expected.

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?

Names a specific verb+resource ('HNWI tax profile for a country') and enumerates the exact data domains covered (income, capital gains, inheritance, wealth tax, exit tax, CRS/AEOI, special regimes). This clearly separates it from siblings like get_country, withholding_map, find_low_tax, and forced_heirship_risk.

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?

Gives concrete triggering questions ('which canton taxes least', 'Geneva vs Zug') tied to the subnational field, which is genuinely useful routing guidance. It stops short of explicitly naming what to use instead for pure tax-rate comparisons (e.g. withholding_map) or for non-HNWI/entity questions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mirabello Immigration Intelligence 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.