Skip to main content
Glama

Second passport: citizenship route and reach

passport_profile
Read-onlyIdempotent

What Patrician.ch publishes on a passport, for more than 60 countries: visa free destinations, the years of residence to citizenship, whether dual citizenship is allowed, any citizenship or residence by investment route, whether the country taxes citizens who live abroad, and the patrician.ch page. Use it for second passport, dual citizenship, naturalization and citizenship by investment questions.

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": {
      "country": "<country>"
    },
    "name": "passport_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesThe passport country, for example Portugal, Malta, Switzerland, Italy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: the data coverage is limited to 60+ countries and the response includes a patrician.ch reference page, which tells the agent what to expect without an output schema. It does not mention rate limits, auth, or staleness of citizenship rules, keeping it short of a 5.

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 resource and its field inventory, then closes with a usage sentence; every clause earns its place by naming a distinct data attribute. The enumerated list is long but functional, with minor redundancy in repeating 'patrician.ch' twice.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read-only lookup with no output schema, the description does the necessary work by enumerating the returned fields and stating country coverage. Auth, rate limits, and pagination are absent, but for a static reference lookup that may genuinely not matter; only the lack of any response-shape caveat (e.g., missing data for unsupported countries) keeps it from a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter with 100% schema description coverage, including concrete examples (Portugal, Malta, Switzerland, Italy). The description adds no further syntax, format, or input constraints, so the baseline 3 applies — the schema carries all parameter meaning.

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 names the concrete resource (a passport profile from Patrician.ch) and enumerates the specific fields it returns: visa-free destinations, residence years to citizenship, dual citizenship rules, investment routes, expat taxation, and the source page. That is far more specific than the title alone and distinguishes it from siblings like place_profile or income_tax_by_place, though it never explicitly contrasts with 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?

The final sentence gives explicit use cases: second passport, dual citizenship, naturalization, and citizenship-by-investment questions. It tells the agent when to reach for this tool but offers no exclusions or named alternatives (e.g., when to use income_tax_by_place instead for tax questions), so routing is clear but not fully disambiguated.

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.

Resources