Mirabello Immigration Intelligence

Filter Company Structures

find_formation_jurisdictions

Read-onlyIdempotent

Filter reference profiles by facts: remote_only, max_setup_usd, banking_tier (good or moderate access), eu_clean (not on EU or FATF lists at the dated snapshot), lane (company or trust). Results are alphabetical, not ranked or recommended. General information, not advice.

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

Input Schema

Name	Required	Description
`lane`	No	company \| trust
`limit`	No	Maximum results returned (default 12, up to 100). The list is ranked; total_matched gives the full count.
`eu_clean`	No	True to require the jurisdiction be absent from EU tax and AML listings.
`remote_only`	No	True to return only options that can be completed without travelling to the country.
`banking_tier`	No	good \| moderate (minimum acceptable)
`max_setup_usd`	No	Maximum acceptable set-up cost in USD.

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

addedInput schema / properties / limit

Added value: +{
+  "description": "Maximum results returned (default 12, up to 100). The list is ranked; total_matched gives the full count.",
+  "examples": [
+    12
+  ],
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

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

Changed4 schema fields changedSep 23, 2026

addedInput schema / properties / eu_clean / description

Added value: +"True to require the jurisdiction be absent from EU tax and AML listings."

addedInput schema / properties / max_setup_usd / description
```
Added value: +"Maximum acceptable set-up cost in USD."
```
addedInput schema / properties / max_setup_usd / examples
```
Added value: +[
+  25000
+]
```

addedInput schema / properties / remote_only / description

Added value: +"True to return only options that can be completed without travelling to the country."

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 25, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Useful behavioral context is added beyond the readOnly/idempotent annotations: results are unranked and explicitly not recommendations, and the EU/FATF screening is pinned to a dated snapshot. However, 'Results are alphabetical' directly conflicts with the limit parameter's schema text ('The list is ranked'), leaving the agent unsure of the true ordering.

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?

Three tight sentences, front-loaded with the filter vocabulary and followed by ordering and disclaimer caveats. The parameter enumeration is somewhat redundant given complete schema descriptions, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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-shape explanation is correctly omitted, and the disclaimer covers the advisory boundary. What is missing is the ordering question raised above and any guidance on combining these filters with sibling discovery tools, which matters for a 6-parameter optional-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 coverage is 100%, so the baseline is 3. The description adds some nuance (banking_tier means minimum acceptable access, eu_clean covers both EU and FATF lists), but it repeats what the schema already states and omits limit entirely, so it does not meaningfully extend parameter meaning.

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?

Names a specific verb and resource ('Filter reference profiles') and enumerates the exact filter dimensions, so an agent can tell it produces a filtered jurisdiction list rather than a comparison or detail lookup. It stops short of naming siblings such as find_trust_jurisdictions or find_low_tax, even though the 'lane' parameter overlaps with those tools.

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 only implied: an agent can infer this is the discovery step before compare_formation or get_company_formation, but the description never says so or states when to prefer a sibling. 'General information, not advice' sets a scope boundary but is not routing guidance.

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.