Skip to main content
Glama

mcp-server

by io.github.mirabello-consultancy
OverviewDiscussionsAdmin

Regulator Registry

get_regulator_registry
Read-only

Registry of the regulatory bodies that govern tax, company formation, accounting, treaties and banking per jurisdiction — ranked most-to-least important, with official-source links (tax authority, company registrar, financial/AML regulator, central bank, specialists like FDIC, DFSA, ADGM FSRA, Cayman CIMA) — plus the international layer (FATF, EU Code of Conduct list, OECD, DG TAXUD, FSB). Pass cc for one jurisdiction, or international:true for the supranational bodies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNoISO alpha-2 (or roster key like MY-LABUAN, KZ-AIFC)
internationalNoTrue to include international/offshore structures rather than domestic-only options.

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
    • addedInput schema / properties / international / description
      Added value: +"True to include international/offshore structures rather than domestic-only options."
  3. 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"
+}
  4. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description does not contradict it. The description usefully adds that results are ranked most-to-least important and carry official-source links, but says nothing about auth needs, coverage gaps or freshness of the registry.

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?

A single front-loaded sentence establishes the resource first, then the invocation modes, with the long parenthetical example lists doing most of the bulk. It is efficient, though the inline examples (FDIC, DFSA, ADGM FSRA, Cayman CIMA) make it denser than needed for an agent's decision.

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?

With an output schema present, the description needn't document return fields, and it still covers both parameters and the content categories. For a two-parameter read-only lookup this is close to complete; only the mismatch between 'supranational bodies' and the schema's 'offshore structures' leaves a small ambiguity.

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 the baseline is 3, but the description adds real meaning: it clarifies that 'cc' selects one jurisdiction and that international:true retrieves the supranational bodies (FATF, EU Code of Conduct, OECD, DG TAXUD, FSB). This reframes the boolean's intent beyond the schema's vaguer 'international/offshore structures' wording, though the two phrasings sit slightly at odds.

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?

The description names a specific resource (registry of regulatory bodies) and enumerates its scope precisely: tax, company formation, accounting, treaties, banking, plus the supranational layer. An agent can distinguish this from get_country_tax, get_banking_access or get_country without opening any schema.

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?

It says how to invoke the two modes ('Pass cc for one jurisdiction, or international:true for the supranational bodies'), which is invocation guidance rather than when-to-use guidance. It never states when this tool should be preferred over siblings such as get_country or get_banking_access, nor any exclusions, so usage is only implied.

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