Mirabello Immigration Intelligence

Maltese Citizen Services

get_malta_citizen_service

Read-onlyIdempotent

Official procedure facts for Maltese citizens and their families, in Malta and abroad: (1) passport renewal (Identità fees by age and season, the official 4-hour urgent service in Malta, applying through a mission abroad, minors, lost/stolen); (2) a newborn's birth registration, citizenship and first passport (born in Malta or abroad to a Maltese parent); (3) a foreign spouse's citizenship by marriage (Cap. 188 art. 6, Form B, 5-year rule); (4) registration by descent (art. 5(3), Forms K and M, two consecutive Malta-born generations; the 1 August 2028 dates concern the parent or ancestor, not an application deadline). Returns steps, documents, itemised fees with source and verified flag, timelines, the authority, missions for the residence country and how Mirabello prepares the file. NOT investment citizenship (Malta's investor programme closed in 2025). Omit service for an overview. Information, not legal advice.

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_malta_citizen_service"
  }
}

Input Schema

Name	Required	Description
`service`	No	Which service: "passport-renewal" (renew a Maltese passport), "newborn" (register a birth, prove citizenship, first passport), "marriage" (foreign spouse of a Maltese citizen), "descent" (planned). Omit for an overview of all services.
`applicant_age`	No	Age in years of the person the passport is for (passport service only); selects the minors rules and fee band.
`residence_country`	No	Where the applicant lives now, as a country name or ISO code (e.g. "Australia", "GB", "Malta"). Selects the in-Malta or abroad procedure and the nearest Maltese missions.

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

AddedOct 15, 2026
RemovedOct 13, 2026
AddedOct 13, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare a read-only, idempotent, closed-world, non-destructive tool, so the safety profile is covered. The description adds real value beyond that: it discloses what is returned (steps, documents, itemised fees with source and verified flag, timelines, authority, nearest missions, Mirabello prep), which tells the agent how authoritative and how citable the output is. It also pre-empts a likely misreading of the 1 August 2028 dates.

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?

It is a single front-loaded paragraph with zero filler — every clause maps to a distinct service or constraint. It is dense to the point of being hard to scan (nested parentheses and semicolons), which costs a little against a perfect score, but no sentence is redundant.

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, the description needn't spell out return structure, and it still gives the agent scope, exclusions, per-service depth, and a legal-advice disclaimer. For a three-parameter, all-optional lookup tool, nothing an agent needs in order to call it correctly is 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 a baseline of 3 is warranted, but the description goes further by expanding what each service value actually contains (age/season fee bands for passports, Cap. 188 art. 6 and the 5-year rule for marriage, Forms K and M plus two-generation rule for descent), which materially helps the agent pick the right enum value. It also clarifies that the 2028 dates are about the ancestor, not a filing deadline.

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?

The description opens with a clear resource (official procedure facts for Maltese citizens) and enumerates four concrete service areas with the statutes and forms attached to each, so an agent knows exactly what content lives here. It also excludes investment citizenship by name. It stops short of naming overlapping siblings such as get_passport_renewal or check_maltese_citizenship_eligibility, so the boundary with those tools must be inferred.

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?

Usage is well signalled: 'Omit service for an overview', the exclusion of Malta's closed investor programme, and 'Information, not legal advice'. The schema-level note that applicant_age is passport-only and residence_country selects in-Malta vs abroad further steers invocation. What's missing is explicit routing to alternatives when the user only wants a fee estimate or a pure eligibility check, both of which have dedicated siblings.

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.