mcp-server

Find Low-Tax Jurisdictions

find_low_tax

Read-only

Find countries by wealth-protection tax criteria — no personal income tax, no inheritance tax, no wealth tax, no capital gains tax, territorial taxation, non-CRS (no automatic financial-account exchange), not on the EU tax black/grey list, or crypto-friendly (favourable crypto-asset tax regime). Returns matching countries with their HNWI tax + CRS + EU-list (+ crypto) snapshot. Combine with a residence or citizenship route for a full tax-plus-pathway view.

Input Schema

TableJSON Schema

Name	Required	Description
`non_crs`	No	True to restrict to jurisdictions outside the CRS automatic-exchange network. Note: Mirabello advises full tax compliance; this is a factual filter, not a concealment tool.
`territorial`	No	True to require a territorial tax system (foreign income untaxed).
`no_income_tax`	No	True to require no personal income tax.
`no_wealth_tax`	No	True to require no net-wealth tax.
`not_eu_listed`	No	True to exclude jurisdictions on the EU list of non-cooperative tax jurisdictions.
`crypto_friendly`	No	True to require a favourable published treatment of digital assets.
`no_inheritance_tax`	No	True to require no inheritance or estate tax.
`no_capital_gains_tax`	No	True to require no capital-gains tax.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present only when the request could not be fulfilled.
`terms`	No	Acceptable-use and information-not-advice terms.
`source`	No	Attribution for the data.
`provider`	No	Always "Mirabello Consultancy".
`disclaimer`	No	Information, not legal/tax/financial/immigration advice; figures indicative.
`data_updated`	No	Date the underlying dataset was last updated.
`book_a_consultation`	No	URL to book a Mirabello consultation.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 23, 2026

addedInput schema / properties / crypto_friendly / description

Added value: +"True to require a favourable published treatment of digital assets."

addedInput schema / properties / no_capital_gains_tax / description
```
Added value: +"True to require no capital-gains tax."
```
addedInput schema / properties / no_income_tax / description
```
Added value: +"True to require no personal income tax."
```
addedInput schema / properties / no_inheritance_tax / description
```
Added value: +"True to require no inheritance or estate tax."
```
addedInput schema / properties / no_wealth_tax / description
```
Added value: +"True to require no net-wealth tax."
```

addedInput schema / properties / non_crs / description

Added value: +"True to restrict to jurisdictions outside the CRS automatic-exchange network. Note: Mirabello advises full tax compliance; this is a factual filter, not a concealment tool."

addedInput schema / properties / not_eu_listed / description

Added value: +"True to exclude jurisdictions on the EU list of non-cooperative tax jurisdictions."

addedInput schema / properties / territorial / description

Added value: +"True to require a territorial tax system (foreign income untaxed)."

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"
+}

Changed1 schema field changedJun 27, 2026
- addedInput schema / properties / crypto_friendly
```
Added value: +{
+  "type": "boolean"
+}
```
AddedJun 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare the tool read-only and non-destructive; the description adds that it 'returns matching countries with their HNWI tax + CRS + EU-list (+ crypto) snapshot' and clarifies that non-CRS means 'no automatic financial-account exchange.' No contradictions with annotations.

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 sentences front-load the purpose and filter list, and the final sentence adds useful combination guidance without padding. Every sentence earns its place for an 8-filter tool.

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 full schema coverage, read-only annotations, and an output schema, the description covers what the tool finds and what it returns. The only notable omission is explicit AND/OR behavior across multiple filters, which is a minor gap for a boolean-filter tool.

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 the baseline is 3; the description groups the boolean criteria and paraphrases a few terms, but it does not add substantial meaning beyond the schema. It also leaves combination semantics (whether multiple true booleans are ANDed) implicit.

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 opens with 'Find countries by wealth-protection tax criteria' and enumerates eight concrete filters, making the action, resource, and scope unmistakable. It is clearly distinguished from sibling search tools like find_trust_jurisdictions or find_formation_jurisdictions by centering on tax/wealth-protection criteria rather than entity type or pathway.

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?

It gives clear context: this tool is for tax-criteria screening and returns a tax-plus-CRS/EU snapshot, and it explicitly recommends combining with a residence or citizenship route for a full tax-plus-pathway view. It does not, however, spell out when-not-to-use it or directly name sibling alternatives, so exclusions are left implicit.

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

All mcp-server 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.