mcp-server

Banking Access Landscape

get_banking_access

Read-only

NON-RESIDENT banking-access landscape per jurisdiction (US, AE, SG, HK, CH, LI, KY/Caribbean, plus the cross-jurisdiction EMI layer): corporate and personal lanes, fintech vs traditional institutions with indicative timelines/minimums, the common REJECTION causes, and CBI/Golden-Visa synergy facts (e.g. the UAE Golden Visa converts a hard non-resident case into an easy resident one; Caribbean correspondent de-risking realities for CBI clients; Swiss/Liechtenstein private-banking entry points). Honest doctrine: no account is ever guaranteed — file quality and right-institution matching are the real product. Pass cc (or EMI); pass type corporate|personal to focus; omit cc for the coverage list. Information, not advice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cc`	No	ISO alpha-2 (US, AE, SG, HK, CH, LI, KY) or EMI for the e-money layer
`type`	No	corporate \| personal (omit for both)

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

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

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description usefully adds that output is 'Information, not advice' and that 'no account is ever guaranteed', setting expectations about the tool's limits and non-actionable nature. It does not cover rate limits or output format, but with annotations carrying the safety profile this is clear added context.

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 resource and scope, but the long parenthetical enumerations and 'Honest doctrine' framing add bulk. Most content is informative, yet it could be tightened without losing the key routing and usage facts.

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

Completeness3/5

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

An output schema exists, so return values need not be explained. Still, for a tool with a near-duplicate sibling (get_nonresident_banking), the description omits any differentiation, leaving an agent uncertain when to choose this one. Otherwise coverage of content and caveats is adequate.

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 schema already documents cc and type. The description still adds value beyond the schema: it specifies 'omit cc for the coverage list' and clarifies type is passed 'to focus', details absent from the schema descriptions.

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 the specific resource (non-resident banking-access landscape per jurisdiction) and scope (corporate/personal lanes, timelines, rejection causes, CBI synergy), making the tool's function clear. However, it does not distinguish itself from sibling get_nonresident_banking, which appears to cover similar ground, so it falls short of full sibling 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?

Provides calling instructions ('Pass cc... omit cc for coverage list') and notes 'Information, not advice', but offers no explicit when-to-use vs alternatives and never names the sibling get_nonresident_banking. Usage is implied rather than guided, matching a 3.

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.