mcp-server

Find Formation Jurisdictions

find_formation_jurisdictions

Read-only

FILTER the Mirabello formation profiles to find company/structure jurisdictions matching constraints: remote_only (fully remote formation), max_setup_usd (setup cost ceiling), banking_tier (good|moderate — minimum), eu_clean (exclude EU Annex I/II and FATF-listed), lane (company|trust). Each match returns key, vehicle, tier, status, headline tax line, cost ranges, timeline, banking tier and ideal-client line, with the full honest per-jurisdiction profile available on request. Rule zero: profit tax follows the OWNER (residence/PoEM/CFC), not the entity. Information, not advice.

Input Schema

TableJSON Schema

Name	Required	Description
`lane`	No	company \| trust
`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

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.

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

A3.6/5.0

Behavior4/5

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

With readOnlyHint=true and destructiveHint=false already in annotations, the description adds valuable context: it discloses the shape of the returned matches, notes that full profiles are not returned inline but are 'available on request', and flags a domain rule about profit tax following the owner. It also adds the 'Information, not advice' disclaimer. It does not mention auth or rate limits, but for a read-only filter tool this is reasonable.

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 description is front-loaded with 'FILTER' and the main purpose, then packs the constraints, return fields, and caveats. It is dense but reasonably organized, with each sentence adding some value. It is slightly longer than necessary because it lists return fields that are likely covered by the output schema.

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?

For a tool with 5 optional parameters and an output schema, the description covers filtering semantics, returned fields, and a domain caveat. However, it never states what happens when no constraints are provided (e.g., returns all jurisdictions or requires at least one filter), which is a notable gap given all parameters are optional.

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 parameters are already documented well. The description mostly restates the schema, with slight expansions like 'eu_clean' meaning 'exclude EU Annex I/II and FATF-listed' and 'remote_only' meaning 'fully remote formation.' This adds marginal clarity but does not materially go beyond the schema's descriptions.

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 clearly states a specific verb ('FILTER'), a resource ('Mirabello formation profiles'), and the purpose (find jurisdictions matching constraints). It enumerates the constraint dimensions, making the tool's function concrete. However, it does not explicitly distinguish itself from overlapping siblings like find_trust_jurisdictions or find_charity_jurisdictions.

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?

The phrase 'find company/structure jurisdictions matching constraints' implies when to use the tool, and the constraint list tells the agent what kind of selection it can perform. But there is no explicit guidance about when NOT to use this tool or which sibling tool to choose for related but different searches, so the guidance is only implied, not explicit.

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.