Expatriator Immigration Knowledge

search_immigration_knowledge

Search Expatriator's curated immigration knowledge base of gotchas — "the official guidance says X but reality is Y" — with severity levels and workarounds. Covers Spain (deepest), Portugal, and general immigration pitfalls.

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": "search_immigration_knowledge"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max results (default 5, max 20)
`query`	No	Natural-language search query
`country`	No	ISO country code filter, e.g. ES, PT
`severity`	No	Minimum severity to return
`procedure`	No	Procedure filter, e.g. nationality, tie_renewal, nie, padron

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 25, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the nature of the data (curated gotchas, severity levels, workarounds). However, it says nothing about whether results are ranked, paginated, or how the severity ordering interacts with the optional filters, so behavioral detail is partial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with what the tool searches and followed by coverage scope. No filler or restatement of the name.

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

Completeness3/5

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

For a five-parameter search tool with no annotations and no output schema, the description explains the domain well but omits result behavior (ordering, pagination, result shape) and gives no guidance on combining the severity/country/procedure filters, leaving gaps an agent would have to discover empirically.

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?

Schema description coverage is 100% and every parameter is documented in the schema, including the enum and examples for country/procedure. The description adds the thematic framing but no syntax or semantics beyond what the schema already provides, so baseline 3 applies.

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 (search) and a distinctive resource (curated immigration knowledge base of 'gotchas' with severity levels and workarounds), and even quotes the content's spirit ('official guidance says X but reality is Y'). This is clearly separable from the sibling procedure-guide and padron tools.

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?

It gives useful context on scope ('Covers Spain (deepest), Portugal, and general immigration pitfalls'), which helps an agent decide when it's useful, but it never states when to prefer this over get_procedure_guide or list_procedure_guides, nor any exclusions.

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

All Expatriator Immigration Knowledge 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.

Resources

Need Help?