Skip to main content
Glama

mcp-server

by io.github.mirabello-consultancy
OverviewDiscussionsAdmin

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
NameRequiredDescriptionDefault
laneNocorporate | trust | personal | watchlist (omit for full roster)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent only when the request could not be fulfilled.
termsNoAcceptable-use and information-not-advice terms.
sourceNoAttribution for the data, when it is not Mirabello Consultancy itself.
book_urlNoLink to request a consultation with a Mirabello specialist, for a personal case.
providerNoAlways "Mirabello Consultancy".
disclaimerNoInformation, not legal/tax/financial/immigration advice; figures indicative.
data_updatedNoDate the underlying dataset was last updated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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."
  2. Changed1 schema field changed
    • 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"
+}
  3. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld=false). The description adds genuinely non-structured context: the screen breadth (~195 countries), the curation doctrine (Mirabello Standard: EU/FATF list hygiene, bankability), and the existence of pending re-rating entries. It does not state freshness/refresh cadence for the watchlist, which would be the next useful disclosure.

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?

Front-loaded with the core noun phrase, but the middle is a dense parenthetical jurisdiction dump and the closing sentence duplicates the lane parameter already in the schema. It is informative but padded, with two 'Mirabello' mentions and a trailing filter note that earns little.

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 one-parameter, read-only catalogue with an output schema present, the description supplies enough framing (domain screen, curation standard, watchlist caveat) for an agent to call it correctly. Return shape is rightfully left to the output schema.

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% and the single 'lane' parameter is fully documented (including the watchlist value), so the schema carries the load. The description repeats the lane menu and omits the watchlist option it actually documents in the schema, adding no syntax or semantic value beyond it; baseline 3 applies.

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?

States concretely what the tool returns: a curated roster of A-tier company-formation jurisdictions, trust situs options, personal-tax-residence regimes, plus a watchlist. This is far more informative than a tautology, though it never names sibling tools (find_formation_jurisdictions, find_trust_jurisdictions, find_low_tax) that appear to cover overlapping territory, so the agent must infer differentiation.

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: the reader can guess this is a browse-the-catalogue tool that can optionally be narrowed by lane. There is no explicit 'use this instead of X when Y' and no mention of how it relates to find_formation_jurisdictions, find_trust_jurisdictions, or get_structuring_playbook, which is the main gap for a roster tool in a dense sibling set.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcp-server toolsInspect
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.

Resources