Skip to main content
Glama

Mirabello Immigration Intelligence

Maltese Passport Fee Estimate

estimate_malta_passport_fee
Read-onlyIdempotent

Itemised official government fee for a Maltese passport (Identità): age band (under 10 / 10-15 / 16+), seasonal adult rate (€70 September-March, €80 April-August), the official urgent service (€160 adult, 4 working hours, in Malta only), the €15 supplement when a lost or stolen passport was still valid, and, for applications through a Maltese embassy or consulate abroad, the mission processing fee and courier charges (flagged where unverified). Deterministic: computed from the official fee table with sources. Information only; confirm with the Passport Office or mission before paying.

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": {
      "age": "<age>"
    },
    "name": "estimate_malta_passport_fee"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageYesAge in years of the passport holder on the application date.
monthNoMonth of application, 1-12 (adult standard fee is €80 April-August, €70 otherwise). Defaults to the current month.
urgentNoTrue for the official urgent service (4 working hours in Malta; from abroad the urgent fee applies but no 4-hour timeframe).
locationNo"malta" if applying at the Passport Office in Malta, "abroad" if applying through a Maltese embassy, high commission or consulate.
lost_still_validNoTrue if the passport being replaced was lost, stolen or destroyed while still valid (adds the €15 oath supplement; a Maltese police report is required).

Output Schema

NameRequiredDescriptionDefault
errorNo
termsNo
sourceNo
book_urlNo
providerNo
disclaimerNo
data_updatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • 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."
  2. Added
  3. Removed
  4. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the description earns credit for adding substance: it is deterministic, derived from the official fee table with sources, flags unverified mission fees, and is explicitly information-only with a confirm-before-paying warning. It does not describe output shape, but an output schema exists, so that is not a real gap.

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?

Front-loads the resource and the component breakdown, then closes with the determinism and information-only caveats in short sentences. The middle is one long enumerated sentence, but each clause corresponds to a distinct fee component, so 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 read-only calculator with five well-documented parameters and an output schema, the description covers every input dimension (age, season, urgency, location, lost-while-valid) plus sourcing and verification caveats. Nothing needed to call it correctly 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 the baseline is 3; the description goes beyond it by supplying the age bands (under 10 / 10-15 / 16+) that the schema does not state, plus the linkage between location=abroad and mission processing/courier charges. The specific euro amounts largely duplicate what the schema descriptions already say, which limits it to a 4 rather than a 5.

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 and resource — an itemised government fee estimate for a Maltese passport — and enumerates exactly what the estimate decomposes into (age band, seasonal rate, urgent service, lost-passport supplement, mission fees abroad). This lets an agent distinguish it from siblings like estimate_total_cost or get_passport_renewal without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The scope is implied clearly (a fee-only, information-only estimate), and the closing caveat about confirming with the Passport Office is useful. But no sibling is named and no when-to-use/when-not rule is given — an agent gets no help choosing this over estimate_total_cost or get_passport_renewal.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.