mcp-server

Global Structuring Roster

get_structuring_roster

Read-only

Mirabello curated GLOBAL STRUCTURING roster from a full ~195-country screen: A-tier company-formation jurisdictions (UAE free zones/ADGM, US LLC, Switzerland, Singapore, Cyprus, Malta, Hungary, Jersey, Mauritius, Luxembourg, Ireland...), trust situs options, personal-tax-residence regimes, plus the watchlist of pending re-ratings (e.g. Monaco FATF delisting). Governed by the Mirabello Standard (EU/FATF list hygiene, bankability, transparency, executability, reputation). Optionally filter by lane: corporate, trust, personal.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lane`	No	corporate \| trust \| personal \| watchlist (omit for full roster)

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.

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

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows it is a safe read. The description adds useful context about the curation criteria (Mirabello Standard, EU/FATF hygiene) and the scope (195-country screen). It does not describe output format or pagination, but that is covered by the output schema. The description adds value beyond annotations without contradicting them.

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 reasonably concise, front-loaded with the core purpose, and includes a useful list of jurisdictions and standards. It is not overly verbose, and every sentence contributes to understanding the tool's scope. The structure flows well from purpose to content to optional filtering.

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?

Given the tool has one optional parameter and an output schema, the description is fairly complete. It explains what the roster contains, the curation standard, and the optional filter. The only minor gap is the omission of the 'watchlist' lane in the filter options, but this is mentioned in the roster description itself. Overall, an agent can correctly invoke the tool with confidence.

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?

The schema covers 100% of the parameters (the single 'lane' parameter is documented with its allowed values). The description adds that the filter is optional and lists the lanes as 'corporate, trust, personal', but omits 'watchlist' which is present in the schema. This is a minor discrepancy, but overall the description reinforces the parameter meaning without adding substantial new information.

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 that this tool provides a curated global structuring roster covering company-formation jurisdictions, trust situs, personal-tax-residence regimes, and a watchlist. It uses specific verbs ('curated', 'filter') and describes the resource. However, it does not differentiate itself from siblings like get_structuring_playbook or get_wealth_atlas, so it misses the top score.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. The description implies it is for obtaining a roster, but it does not mention when to prefer it over similar tools (e.g., find_formation_jurisdictions, get_structuring_playbook). It also does not state conditions where it should not be used.

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.