Mirabello Immigration Intelligence

Passport Validity & Health Entry Rules

get_entry_requirements

Read-onlyIdempotent

ENTRY REQUIREMENTS for a DESTINATION: passport-validity rule (the "6-month rule", the Schengen "issued within the previous 10 years AND valid 3 months beyond departure" cap, blank-page requirements) and health/vaccination entry rules (e.g. yellow-fever certificate). Operationally critical: a valid-looking passport is refused BOARDING if it fails these, and the Schengen 10-year issuance cap invalidates passports whose printed expiry is still in the future. Pass cc for one destination; omit for all. Information, not advice — rules and airline enforcement vary by nationality and change without notice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_entry_requirements"
  }
}

Input Schema

Name	Required	Description	Default
`cc`	No	ISO alpha-2 destination country code

Output Schema

Name	Required	Description	Default
`error`	No
`terms`	No
`source`	No
`book_url`	No
`provider`	No
`disclaimer`	No
`data_updated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 25, 2026

changedOutput schema / description

Previous value: -"Mirabello response envelope. Tool-specific fields vary; the provenance/disclaimer envelope is always present."New value: +"Mirabello envelope; tool fields vary; error only on failure."

removedOutput schema / properties / book_url / description

Removed value: -"Link to request a consultation with a Mirabello specialist, for a personal case."

removedOutput schema / properties / data_updated / description

Removed value: -"Date the underlying dataset was last updated."

removedOutput schema / properties / disclaimer / description

Removed value: -"Information, not legal/tax/financial/immigration advice; figures indicative."

removedOutput schema / properties / error / description

Removed value: -"Present only when the request could not be fulfilled."

removedOutput schema / properties / provider / description
```
Removed value: -"Always \"Mirabello Consultancy\"."
```

removedOutput schema / properties / source / description

Removed value: -"Attribution for the data, when it is not Mirabello Consultancy itself."

removedOutput schema / properties / terms / description

Removed value: -"Acceptable-use and information-not-advice terms."

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

AddedJul 29, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond readOnly/idempotent annotations, the description explains operationally critical consequences: boarding refusal despite a valid-looking passport, the Schengen 10-year issuance cap, and nationality-dependent airline enforcement. This adds substantial behavioral context not present in the structured 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 front-loaded with the core purpose and contains no filler, but the first sentence is dense and packs multiple examples into one long clause. It remains readable and every sentence adds value.

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?

With an output schema present and only one optional parameter, the description covers the key missing context: purpose, operational impact, parameter omission behavior, and limitations around nationality and changing rules. Nothing critical for correct invocation appears absent.

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 that cc is an ISO alpha-2 destination country code. The description adds important semantics by stating that passing cc returns one destination and omitting it returns all destinations.

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 states a specific resource and scope: destination entry requirements covering passport-validity rules and health/vaccination rules. It distinguishes this from broader visa-checking siblings by emphasizing passport validity, blank pages, yellow-fever certificates, and airline boarding enforcement.

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 clear usage context, including 'Pass cc for one destination; omit for all,' which tells the agent how to scope the call. It does not explicitly name sibling alternatives such as check_visa_requirement, but its scope is sufficiently clear to avoid likely misuse.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mirabello Immigration Intelligence 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.