mcp-server

Digital-Government Progress

get_digital_gov_progress

Read-only

Per-country digital-money & identity progress relevant to wealth planning: (1) CBDC status (none/researching/exploring/pilot/launched) + type (retail/wholesale) and issuer; (2) government-issued or government-sanctioned STABLECOIN status + regulatory framework (e.g. MiCA, MAS, GENIUS Act); (3) national DIGITAL ID status (planned/piloting/operational/mandatory), legal framework, biometric/mobile, cross-border interoperability (eIDAS/EUDI) and privacy law. Each block carries provenance (confidence, verified_date, official sources); low-confidence detail is withheld as CHECK-OFFICIAL-SOURCE. Pass cc for one jurisdiction, omit for all. INFORMATION, NOT ADVICE — government status/timelines change frequently; verify the cited source.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cc`	No	ISO 3166-1 alpha-2 country code, uppercase (e.g. "PT" Portugal, "AE" United Arab Emirates, "KN" St Kitts and Nevis).

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.

Changed2 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"
+]
```

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

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare readOnlyHint and destructiveHint, so the description carries the burden of explaining behavior. It goes beyond that by disclosing provenance fields, the CHECK-OFFICIAL-SOURCE withholding behavior for low-confidence details, and the advisory nature with 'INFORMATION, NOT ADVICE.' This is exactly the kind of behavioral context an agent needs.

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 longer than average, but it earns its length by packing three distinct content categories into a clear numbered structure. The lead sentence front-loads the purpose before diving into details, and the caveats at the end are concise.

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?

For a read-only data tool with a single optional parameter and an output schema, the description covers everything needed to select and invoke it: scope, parameter behavior, provenance, confidence handling, and verification expectations. Nothing critical is missing.

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?

With 100% schema description coverage, the schema already fully documents the optional cc parameter, including format, examples, and case sensitivity. The description adds one useful nuance—omitting cc returns all jurisdictions—but it does not add substantial new semantic detail beyond the schema.

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 verb and resource: 'Per-country digital-money & identity progress relevant to wealth planning.' It then enumerates three concrete content areas (CBDC status, stablecoin status, digital ID status), which clearly distinguishes it from sibling getters like get_country or get_recent_changes.

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?

The description states the scope and the cardinality rule: 'Pass cc for one jurisdiction, omit for all.' It also warns that statuses change and to verify sources, giving the agent a clear sense of when the tool is appropriate. It does not explicitly compare against alternatives, but the purpose is specific enough to make the intended use obvious.

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.