mcp-server

Compliance Checklist

compliance_checklist

Read-only

Lists the reporting/compliance obligations a stated profile may trigger — FATCA (US persons), CRS, CARF/DAC8 (crypto), DAC6 (EU cross-border arrangements), PEP enhanced due diligence, investment-migration due diligence, trust/beneficial-ownership reporting and source-of-wealth evidence. Pass boolean flags (us_person, crs_reportable, crypto_holder, dac6, pep, cbi_applicant, trust_settlor, large_cash_or_sow). STATELESS — pass only non-identifying flags, never personal data. Informational only, not legal/tax advice, not exhaustive.

Input Schema

TableJSON Schema

Name	Required	Description
`pep`	No	True if the client is a politically exposed person, a family member or a known close associate — requires enhanced due diligence.
`dac6`	No	True if a reportable cross-border arrangement under EU DAC6 may be involved.
`us_person`	No	True if the client is a US person for tax purposes (citizen, green-card holder or substantial-presence resident) — triggers FATCA and US filing obligations.
`cbi_applicant`	No	True if the client is applying for citizenship by investment.
`crypto_holder`	No	True if the client holds digital assets — relevant to CARF and local crypto reporting.
`rbi_applicant`	No	True if the client is applying for residence by investment.
`trust_settlor`	No	True if the client settles or controls a trust or foundation.
`crs_reportable`	No	True if the client holds financial accounts reportable under the CRS automatic-exchange regime.
`large_cash_or_sow`	No	True if large cash movements or a complex source-of-wealth story are involved.
`eu_cross_border_arrangement`	No	True if the structure spans two or more EU member states.

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.

Changed10 schema fields changedSep 23, 2026

addedInput schema / properties / cbi_applicant / description

Added value: +"True if the client is applying for citizenship by investment."

addedInput schema / properties / crs_reportable / description

Added value: +"True if the client holds financial accounts reportable under the CRS automatic-exchange regime."

addedInput schema / properties / crypto_holder / description

Added value: +"True if the client holds digital assets — relevant to CARF and local crypto reporting."

addedInput schema / properties / dac6 / description

Added value: +"True if a reportable cross-border arrangement under EU DAC6 may be involved."

addedInput schema / properties / eu_cross_border_arrangement / description

Added value: +"True if the structure spans two or more EU member states."

addedInput schema / properties / large_cash_or_sow / description

Added value: +"True if large cash movements or a complex source-of-wealth story are involved."

addedInput schema / properties / pep / description

Added value: +"True if the client is a politically exposed person, a family member or a known close associate — requires enhanced due diligence."

addedInput schema / properties / rbi_applicant / description

Added value: +"True if the client is applying for residence by investment."

addedInput schema / properties / trust_settlor / description

Added value: +"True if the client settles or controls a trust or foundation."

addedInput schema / properties / us_person / description

Added value: +"True if the client is a US person for tax purposes (citizen, green-card holder or substantial-presence resident) — triggers FATCA and US filing obligations."

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

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so no safety concern is hidden. The description adds valuable behavioral context beyond annotations: statelessness, the prohibition on passing personal data, and the non-exhaustive/informational nature of the output.

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 dense, front-loaded with the substantive obligation list, and includes only high-value guardrails afterwards. It earns most of its length, but the parenthetical flag list partially duplicates the schema and is incomplete, so it is not perfectly economical.

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 output schema, full schema parameter coverage, readOnlyHint=true, and zero required parameters, the description is largely sufficient: purpose, privacy behavior, and caveats are all covered. It only lacks an explicit pointer to sibling alternatives and the flag list omits two schema parameters.

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 coverage is 100%, so the schema fully documents all ten boolean flags and the description adds little semantic value beyond relisting some of them as 'boolean flags'. In fact, the parenthetical list omits rbi_applicant and eu_cross_border_arrangement, making the flag list slightly incomplete, but this is not a contradiction.

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 uses the specific verb 'Lists' with the resource 'reporting/compliance obligations a stated profile may trigger' and enumerates the regimes (FATCA, CRS, CARF/DAC8, DAC6, PEP, etc.), which clearly distinguishes it from sibling checklist and eligibility tools even though no sibling is named.

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?

It gives operational guidance on how to invoke the tool ('Pass boolean flags...') and clear boundary conditions ('STATELESS — pass only non-identifying flags, never personal data' and 'Informational only, not legal/tax advice'), so an agent knows when a first-pass compliance screening is intended. It does not explicitly name alternatives or when-not-to-use conditions, so it stops short of a 5.

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.