mcp-server

Maltese Citizenship Screener

check_maltese_citizenship_eligibility

Read-only

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.

Input Schema

TableJSON 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

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, when it is not Mirabello Consultancy itself.
`book_url`	No	Link to request a consultation with a Mirabello specialist, for a personal case.
`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.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the read-only, non-destructive safety profile, but the description adds rich behavioral context: it enumerates the returned outcome values, mentions reasons, form, next steps and sources, and discloses key decision rules (1 August 1989 rule, father-only rule, 5-year marriage rule). It also states the decision authority, going well beyond structured fields.

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 long but front-loads the core purpose and routes before returns and disclaimers. Every sentence carries substantive information, though the heavy parenthetical style makes it slightly dense and less scannable than it could be.

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-parameter screening tool with an output schema and annotations, the description covers purpose, route-specific rules, output outcomes, and legal caveats. An agent has everything needed to select and invoke it correctly; return values are additionally summarized but the output schema already handles that burden.

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 description coverage is 100%, so the baseline is 3. The description still adds legal-rule context that maps to parameters (e.g., how marriage_date drives the 5-year rule, how parent_citizenship_basis interacts with the father-only and registration rules), giving the agent more semantic grounding than the schema alone.

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?

States a specific verb (screen) and resource (Maltese citizenship eligibility) and immediately scopes it to two family routes (birth, marriage). The level of detail distinguishes it from generic siblings like check_eligibility or matrimonial_regime_screen without needing to name them.

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?

Clearly frames the tool as a 'rules-based first screen' and explicitly warns it is 'not a legal determination', which sets expectations for when to use it. However, it does not name any alternative sibling or state when not to use it (e.g., for non-Maltese citizenship checks).

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.