Mirabello Immigration Intelligence

Choice-of-Law Options

choice_of_law_options

Read-onlyIdempotent

Which law may govern a cross-border family succession, matrimonial property and divorce, and whether NATIONALITY opens an election. From nationalities held, habitual residence, asset situs and marital status, returns the default applicable law (EU Succession Reg 650/2012 Art 21; Swiss PILA last domicile), the instruments in scope (650/2012 Art 22; Matrimonial Property Reg 2016/1103 Art 22, 18 states; Rome III Art 5, 17 states; Swiss professio juris Arts 90-91), the elections available, hard TIMING rules (2016/1103 and Rome III need the nationality at the time of the agreement; Swiss professio juris is VOID if Swiss nationality is later acquired), situs overrides (e.g. French Code civil art. 913), and the trade-off: a common-law election swaps a FIXED reserved share for a DISCRETIONARY family claim. Returns no-useful-election where nationality opens nothing. Every election needs a properly executed declaration. INFORMATION ONLY, NOT LEGAL OR TAX ADVICE. Pass ISO alpha-2 codes only, never personal data.

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": "choice_of_law_options"
  }
}

Input Schema

Name	Required	Description
`married`	No	Whether the applicant is married — affects family pricing and some eligibility rules.
`asset_situs`	No	ISO alpha-2 codes where assets are situated.
`nationalities`	No	ISO alpha-2 codes of nationalities held.
`habitual_residence`	No	ISO alpha-2 of current habitual residence.
`spouse_nationalities`	No	Array of the spouse's citizenships as country names.

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

Changed3 schema fields changedSep 23, 2026
- addedInput schema / properties / married / description
```
Added value: +"Whether the applicant is married — affects family pricing and some eligibility rules."
```
- addedInput schema / properties / spouse_nationalities / description
```
Added value: +"Array of the spouse's citizenships as country names."
```
- addedInput schema / properties / spouse_nationalities / examples
```
Added value: +[
+  [
+    "Brazil"
+  ]
+]
```

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

AddedJul 26, 2026

TDQS

A3.8/5.0

Behavior5/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), and the description adds substantial behavior beyond them: hard timing rules (2016/1103 and Rome III require nationality at the time of the agreement), the VOID outcome if Swiss nationality is later acquired, situs overrides like Code civil art. 913, the fixed-versus-discretionary trade-off, and the 'no-useful-election' sentinel. It also warns that every election requires a properly executed declaration and disclaims legal/tax advice.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is all relevant, but it is delivered as a single dense run-on paragraph with heavy mid-sentence capitalization (NATIONALITY, TIMING, VOID, FIXED, DISCRETIONARY). It is front-loaded on the core question, yet a reader must parse a wall of text to extract the timing rules and disclaimers.

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 complex legal-analysis tool with an output schema, an output-schema-free return explanation and a 100%-covered input schema, the description supplies the legal bases, edge-case outcomes and privacy constraint an agent needs to call it correctly. What is missing is only the sibling routing that would clarify when this is preferred over succession_conflict_map or matrimonial_regime_screen.

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 100%, so the schema carries most parameter meaning and the baseline is 3. The description adds format guidance ('Pass ISO alpha-2 codes only, never personal data'), but that guidance conflicts with the sibling schema, which describes spouse_nationalities as 'country names' with the example 'Brazil' — an inconsistency an agent could trip over.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a very specific deliverable set: default applicable law under Reg 650/2012 Art 21 / Swiss PILA, instruments in scope, elections available, timing rules and situs overrides, for cross-border succession, matrimonial property and divorce. That is far beyond a restatement of the name. However it never names an overlapping sibling such as succession_conflict_map or matrimonial_regime_screen, so the boundary between those tools must be inferred.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: 'From nationalities held, habitual residence, asset situs and marital status, returns...' tells the agent what inputs trigger the analysis, and 'Returns no-useful-election where nationality opens nothing' describes a boundary outcome. There is no explicit when-to-use/when-not or routing to succession_conflict_map, matrimonial_regime_screen or forced_heirship_risk, which overlap heavily with this tool.

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.