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, when it is not Mirabello Consultancy itself.
`book_url`	No	Link to request a consultation with a Mirabello specialist, for a personal case.
`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.

Schema Changelog

Changes observed during successful MCP inspections.

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."

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.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, non-openWorld), so the bar is lower. The description adds meaningful detail beyond that by specifying what is returned (HNWI tax + CRS + EU-list (+ crypto) snapshot) and clarifying non-CRS semantics in prose.

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?

Two sentences, front-loaded with the criteria enumeration followed by the return shape and the combination hint. Efficient overall, though the long parenthetical clauses make the first sentence dense.

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?

With an output schema present, return-format explanation is not strictly required, and all 8 params are documented in the schema. The description covers purpose, filters, and a next-step combination, leaving little an agent would need in order to invoke it correctly.

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 every parameter is individually documented with its own clarifying text (including a compliance note on non_crs), so the schema does the heavy lifting. The description's criteria list essentially restates the same filters, adding framing rather than new syntax or edge-case meaning — baseline 3.

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 (Find) and resource (countries) plus the exact filter dimensions, and the criterion list differentiates it from single-country tools like get_country_tax and from sibling finders such as find_formation_jurisdictions or find_charity_jurisdictions. An agent can tell what domain this covers without opening the schema.

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 closing line gives clear forward guidance — 'Combine with a residence or citizenship route for a full tax-plus-pathway view' — which tells the agent how this fits into a workflow. It stops short of naming an explicit alternative tool or a when-not condition, so it is clear context without exclusions.

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.