mcp-server

Passport Renewal Facts

get_passport_renewal

Read-only

CBI passport-RENEWAL facts for a Caribbean/Pacific programme country (St Kitts & Nevis, Antigua & Barbuda, Dominica, Grenada, St Lucia, Vanuatu): official government renewal fees (currency-primary EC$/GBP/VT with USD approximations, adult/child/lost-stolen), passport validity (adult/child years incl. Grenada adult 10-year since Jul 2024 and St Lucia 10-year since Aug 2025), typical processing, remote-renewal capability (Vanuatu requires in-person biometrics), biometric status, ECCIRA status (postponed to mid-2026, existing rules in force), the biometric/ECCIRA deadlines (e.g. St Kitts 31 Jul 2027), official source URLs, last_verified and the Mirabello /passport-renewal page. Pass country (programme id, e.g. st-kitts-cbi) for one; omit for all six. Citizenship is permanent; an expired passport is only a lapsed travel document. Information, not advice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`country`	No	programme id (e.g. st-kitts-cbi, st-lucia-cbi) or country alias; omit for all six

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.

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

TDQS

A4.2/5.0

Behavior4/5

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

With readOnlyHint and destructiveHint already covering the safety profile, the description adds non-obvious context: citizenship is permanent even if a passport lapses, results are information rather than advice, and figures include official sources and last_verified dates. It also scopes approximations and exceptions like Vanuatu in-person biometrics. No contradiction with annotations.

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 but efficient: every clause covers a fact category, an exception, or a caveat, and the target resource is front-loaded. It is a single long run-on paragraph, which slightly hurts scanability, so it does not receive a 5.

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?

Given an output schema exists and annotations characterize safety, the description covers country selection, six-country scope, current rule changes, processing and biometric details, ECCIRA deadlines, source URLs, last_verified, and the information-not-advice disclaimer. Nothing essential for selecting or calling the tool 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?

The input schema already fully documents the country parameter as 'programme id or country alias; omit for all six', and the description essentially restates this with examples. Since schema coverage is 100%, the description adds no new parameter-level meaning, so the baseline of 3 applies.

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 first clause names a specific resource—CBI passport-renewal facts—and immediately delimits the six covered countries and the fact categories included. This goes beyond the tool name and title, and clearly separates it from sibling get_* tools.

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 makes the call context clear: use this tool when passport-renewal facts for these CBI countries are needed, and 'omit for all six' to get broad results. It does not explicitly name alternatives or exclusions, but the resource is specific enough that an agent can route to it safely.

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.