Mirabello Immigration Intelligence

Maltese Citizenship Screener

check_maltese_citizenship_eligibility

Read-onlyIdempotent

Rules-based first screen of whether a person is already Maltese or can register, for two family routes: "birth" (a child born in Malta or abroad to a Maltese parent, the 1 August 1989 rule, the father-only rule for 1964-1989 births abroad and the maternal-line Form I) and "marriage" (spouse of a Maltese citizen, 5 years married and living together, widow/widower and separation cases, the prerequisite of registering a foreign marriage in Malta). Returns an outcome (citizen_automatically | likely_eligible | not_yet_eligible | needs_legal_opinion | out_of_scope), the reasons, the form to use, next steps and official sources. A screen, not a legal determination; the decision rests with Aġenzija Komunità Malta.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "route": "<route>"
    },
    "name": "check_maltese_citizenship_eligibility"
  }
}

Input Schema

Name	Required	Description
`route`	Yes	"birth" to check a child's citizenship by birth/descent, "marriage" to check a foreign spouse's eligibility to register.
`separated`	No	Route marriage: true if the spouses are separated (legally or in fact).
`birth_date`	No	Route birth: the child's date of birth, ISO YYYY-MM-DD.
`born_in_malta`	No	Route birth: true if the child was born in Malta, false if born abroad.
`marriage_date`	No	Route marriage: date of the marriage, ISO YYYY-MM-DD (the 5 years run from this date).
`maltese_parent`	No	Route birth: which parent was a Maltese citizen when the child was born.
`living_together`	No	Route marriage: true if the spouses still live together.
`spouse_deceased`	No	Route marriage: true if the Maltese spouse has died.
`parent_citizenship_basis`	No	Route birth: how the Maltese parent holds citizenship. "registration_by_descent" means the parent registered as a descendant (Forms K/M), citizenship then does not pass automatically.
`marriage_registered_in_malta`	No	Route marriage: true if a marriage celebrated abroad has already been registered at the Malta Public Registry.

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.4/5.0

Behavior4/5

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

Annotations already declare the safe read-only, idempotent, closed-world profile, so the description's burden is lower. It adds genuine value beyond the annotations by listing the full outcome set (citizen_automatically through out_of_scope), the returned artifacts (reasons, form, next steps, official sources), and the legal disclaimer — the kind of disclosure an agent needs to decide whether to escalate.

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?

Information-dense and front-loaded: purpose, routes, then return values and disclaimer. The middle sentence is long with nested parentheses but each clause carries rule-relevant substance rather than filler. Slightly heavy for a single sentence, but nothing is wasted.

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 10-param, rule-driven screener, the description covers what it evaluates, which routes and rules apply, the possible outcomes, the outputs, and the limits of its authority. With an output schema present it need not detail return structure, and no essential calling information is missing.

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 per-dimension baseline is 3. The description adds meaning beyond the schema by explaining the substantive rules that the route parameters trigger — the 1 August 1989 rule, the father-only rule for 1964-1989 births abroad, the maternal-line Form I, and the 5-years-married-and-living-together marriage test — which helps an agent understand why certain flags matter.

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 definition names a specific verb ('rules-based first screen'), a specific resource ('whether a person is already Maltese or can register'), and enumerates the two supported routes with their governing rules. This is narrow enough to be distinguished from broad siblings like check_eligibility, find_pathways, or get_family_pathway without opening the schema.

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 'first screen' framing and the closing 'A screen, not a legal determination; the decision rests with Aġenzija Komunità Malta' give clear context for when this tool is appropriate and where its authority ends. It does not explicitly name a sibling alternative (e.g., book_consultation or get_family_pathway) for cases that fall outside the two routes, so a 4 rather than a 5.

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.