Mirabello Immigration Intelligence

Compare Scenarios

compare_scenarios

Read-onlyIdempotent

Side-by-side comparison of 2-8 jurisdictions across every wealth-protection dimension at once: tax (income/CGT/inheritance/wealth top rates + territorial-vs-worldwide + special regimes), crypto-asset treatment, tax-residence day-count, trust/foundation structure availability, reporting (CRS/EU-list/DAC6) and succession/forced-heirship. The synthesis view over the tax, residence, structure, reporting and succession layers. Pass scenarios as an array of {cc,pathway} or cc as a comma list (e.g. AE,PT,SG). Informational only, not advice; combine with the immigration route and a specific double-tax-treaty corridor for the full picture.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "compare_scenarios"
  }
}

Input Schema

Name	Required	Description	Default
`cc`	No	Country: ISO 3166-1 alpha-2 code (e.g. "PT", "AE", "KN") or its name in any of the 11 site languages ("Portugal", "Schweiz", "UAE"); input_notes shows how it was read.
`scenarios`	No	Array of scenario objects to compare side by side, each naming a programme id and the family composition and options to price.

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.

Changed9 schema fields changedOct 25, 2026

changedInput schema / properties / cc / description

Previous value: -"ISO 3166-1 alpha-2 country code, uppercase (e.g. \"PT\" Portugal, \"AE\" United Arab Emirates, \"KN\" St Kitts and Nevis)."New value: +"Country: ISO 3166-1 alpha-2 code (e.g. \"PT\", \"AE\", \"KN\") or its name in any of the 11 site languages (\"Portugal\", \"Schweiz\", \"UAE\"); input_notes shows how it was read."

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

Changed3 schema fields changedSep 23, 2026

addedInput schema / properties / cc / description

Added value: +"ISO 3166-1 alpha-2 country code, uppercase (e.g. \"PT\" Portugal, \"AE\" United Arab Emirates, \"KN\" St Kitts and Nevis)."

addedInput schema / properties / cc / examples
```
Added value: +[
+  "PT",
+  "AE"
+]
```

addedInput schema / properties / scenarios / description

Added value: +"Array of scenario objects to compare side by side, each naming a programme id and the family composition and options to price."

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

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety bar is low. The description adds real context beyond that: the 2-8 jurisdiction range, the dual input encoding, and an explicit 'informational only, not advice' limitation. No latency/rate/return details beyond what the output schema covers.

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 comparison scope is front-loaded in the first sentence and the routing/disclaimer closes it. The parenthetical dimension list is dense but each item is substantive for a synthesis tool. Slightly long, though nothing is pure filler.

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 and annotations covering the safety profile, the description need not explain returns. It supplies the missing pieces an agent needs: input shape alternatives, cohort size, scope of dimensions, and the informational-only caveat. Only minor gap is the ambiguity between the description's {cc,pathway} and the schema's 'programme id + family composition' wording.

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%, so baseline is 3; the description earns an extra point by contributing what the schema does not: the 2-8 cardinality bound and the alternative comma-list encoding ('AE,PT,SG') for cc. It leaves the scenarios array's pathway/family-composition semantics to the schema, which is acceptable given coverage.

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 and resource ('side-by-side comparison of 2-8 jurisdictions') plus the exact dimensions compared (tax, crypto, residence day-count, structures, reporting, succession). It also positions itself against siblings by calling itself 'the synthesis view over the tax, residence, structure, reporting and succession layers', which distinguishes it from compare_formation, compare_programmes and compare_treaty_position.

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?

Tells the agent this is the aggregate/multi-dimension comparison and to pair it with 'the immigration route and a specific double-tax-treaty corridor' — effectively routing to find_pathways/compare_treaty_position for depth. It stops short of naming those siblings or stating exclusions (e.g. when a narrower comparator is preferable), so it is clear but not fully prescriptive.

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.