mcp-server

Wealth Index

get_wealth_index

Read-only

CLIENT-WEIGHTED wealth-protection composite over the Atlas pillars. Pass your own weights (any of tax_efficiency, structure_strength, residence_clarity, crypto_clarity, succession_certainty, regulatory_transparency, institutional_stability) to score jurisdictions for a SPECIFIC client profile — there is no single public "best" ranking because the right weighting depends on the client. Omit weights for an illustrative default composite. Pass cc for one jurisdiction, or limit for the top N. Pure projection over Mirabello-verified data; illustrative comparative score, NOT advice.

Input Schema

TableJSON Schema

Name	Required	Description
`cc`	No	ISO 3166-1 alpha-2 country code, uppercase (e.g. "PT" Portugal, "AE" United Arab Emirates, "KN" St Kitts and Nevis).
`limit`	No	Maximum number of items to return. Responses can be large; use this to keep the answer small.
`weights`	No	Optional weighting overrides for the index pillars, as an object of pillar name to weight; omit for the published default weights.

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, when it is not Mirabello Consultancy itself.
`book_url`	No	Link to request a consultation with a Mirabello specialist, for a personal case.
`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.

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed5 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 / limit / description

Added value: +"Maximum number of items to return. Responses can be large; use this to keep the answer small."

addedInput schema / properties / limit / examples
```
Added value: +[
+  10
+]
```

addedInput schema / properties / weights / description

Added value: +"Optional weighting overrides for the index pillars, as an object of pillar name to weight; omit for the published default weights."

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

Behavior4/5

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

Annotations already establish this is a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false). The description adds real context beyond that: it is a 'Pure projection over Mirabello-verified data' and an 'illustrative comparative score, NOT advice' — useful provenance and liability framing. It stops short of describing scoring mechanics or precision limits.

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 sentences, front-loaded with the composite's nature, followed by parameter guidance and a disclaimer. Dense but every clause carries information; the parenthetical pillar list is the only mild bulk, and it is load-bearing for the weights object.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite a nested weights object and a real output schema (so return values need not be described), the description covers the composite's meaning, default behavior, single-country mode, top-N mode, data provenance, and scope disclaimer. Nothing needed to invoke it correctly is missing.

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, but the description adds genuine meaning: it enumerates the seven valid pillar keys (tax_efficiency, structure_strength, residence_clarity, crypto_clarity, succession_certainty, regulatory_transparency, institutional_stability), which the nested weights schema does not list, and clarifies cc/limit behavior.

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 ('score jurisdictions', 'CLIENT-WEIGHTED wealth-protection composite') and enumerates the pillars being weighted. It also distinguishes itself from a generic ranking tool and from siblings like get_index/get_wealth_atlas by insisting the result is profile-dependent.

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?

Explains the two operative modes clearly: 'Omit weights for an illustrative default composite' and 'Pass cc for one jurisdiction, or limit for the top N.' It also frames why the tool exists (no single public best ranking), but it doesn't explicitly route the agent away from sibling tools for adjacent questions.

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.