Spain Legal by Legal Fournier

Get Residency Path

get_residency_path

Read-onlyIdempotent

Explain the next permanent-residency or nationality milestone from current status and time in Spain, with explicit caution flags for counting issues.

Input Schema

Name	Required	Description
`current_status`	Yes	Current Spanish immigration or nationality status.
`years_in_spain`	Yes	Years already spent in Spain under the relevant stay or residence history.
`nationality_track`	No	Optional nationality timeline group for a more specific nationality answer.
`continuity_confirmed`	No
`has_absence_concerns`	No	Whether absences or continuity problems may weaken the residence or nationality clock.
`special_nationality_basis`	No	Optional basis for the one-year nationality track when that exception is being claimed.
`qualifying_legal_residence_years`	No

Output Schema

Name	Required	Description
`summary`	Yes	Short explanation of where the person sits on the path.
`milestones`	Yes	Key milestones on the path.
`next_steps`	Yes	Immediate next steps.
`references`	Yes	Secondary Legal Fournier references.
`review_level`	Yes	How much human review is still advisable before treating the result as filing-ready.
`caution_notes`	Yes	Important cautions.
`decision_trace`	Yes	Structured trace of the main timing factors.
`key_rules_applied`	Yes	Stable rules applied by the tool.
`nationality_status`	Yes	Nationality stage given the provided track information.
`related_resource_uris`	Yes	Canonical MCP resources an agent can read next without leaving the server.
`official_legal_sources`	Yes	Official legal sources anchoring the residence and nationality timeline analysis.
`suggested_follow_up_tools`	Yes	Tool calls that are likely to advance the analysis.
`current_verification_flags`	Yes	Live-verification warnings for route, continuity, or timing issues.
`permanent_residency_status`	Yes	Long-term residence stage.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 18, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed4 schema fields changedOct 18, 2026

addedInput schema / properties / continuity_confirmed
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / qualifying_legal_residence_years

Added value: +{
+  "maximum": 120,
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / years_in_spain / maximum
```
Added value: +120
```

changedOutput schema / properties / suggested_follow_up_tools / items / enum

Previous value: -[
-  "find_legal_fournier_tool",
-  "run_legal_fournier_tool",
-  "get_paid_consultation_options",
-  "get_paid_call_availability",
-  "get_visa_options",
-  "check_beckham_eligibility",
-  "get_residency_path",
-  "explain_nie_process",
-  "compare_tax_regimes",
-  "route_to_legal_fournier_help",
-  "create_legal_fournier_contact_request"
-]New value: +[
+  "search",
+  "fetch",
+  "find_legal_fournier_tool",
+  "run_legal_fournier_tool",
+  "get_paid_consultation_options",
+  "get_paid_call_availability",
+  "get_visa_options",
+  "check_beckham_eligibility",
+  "get_residency_path",
+  "explain_nie_process",
+  "compare_tax_regimes",
+  "route_to_legal_fournier_help",
+  "create_legal_fournier_contact_request"
+]

Changed1 schema field changedJul 17, 2026

changedOutput schema / properties / suggested_follow_up_tools / items / enum

Previous value: -[
-  "find_legal_fournier_tool",
-  "run_legal_fournier_tool",
-  "get_visa_options",
-  "check_beckham_eligibility",
-  "get_residency_path",
-  "explain_nie_process",
-  "compare_tax_regimes",
-  "route_to_legal_fournier_help",
-  "create_legal_fournier_contact_request"
-]New value: +[
+  "find_legal_fournier_tool",
+  "run_legal_fournier_tool",
+  "get_paid_consultation_options",
+  "get_paid_call_availability",
+  "get_visa_options",
+  "check_beckham_eligibility",
+  "get_residency_path",
+  "explain_nie_process",
+  "compare_tax_regimes",
+  "route_to_legal_fournier_help",
+  "create_legal_fournier_contact_request"
+]

Changed1 schema field changedMay 13, 2026

changedOutput schema / properties / suggested_follow_up_tools / items / enum

Previous value: -[
-  "find_legal_fournier_tool",
-  "run_legal_fournier_tool",
-  "get_visa_options",
-  "check_beckham_eligibility",
-  "get_residency_path",
-  "explain_nie_process",
-  "compare_tax_regimes",
-  "route_to_legal_fournier_help"
-]New value: +[
+  "find_legal_fournier_tool",
+  "run_legal_fournier_tool",
+  "get_visa_options",
+  "check_beckham_eligibility",
+  "get_residency_path",
+  "explain_nie_process",
+  "compare_tax_regimes",
+  "route_to_legal_fournier_help",
+  "create_legal_fournier_contact_request"
+]

Changed1 schema field changedMay 13, 2026

changedOutput schema / properties / suggested_follow_up_tools / items / enum

Previous value: -[
-  "get_visa_options",
-  "check_beckham_eligibility",
-  "get_residency_path",
-  "explain_nie_process",
-  "compare_tax_regimes",
-  "route_to_legal_fournier_help"
-]New value: +[
+  "find_legal_fournier_tool",
+  "run_legal_fournier_tool",
+  "get_visa_options",
+  "check_beckham_eligibility",
+  "get_residency_path",
+  "explain_nie_process",
+  "compare_tax_regimes",
+  "route_to_legal_fournier_help"
+]

First observedMar 25, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuine behavioral context beyond them: it discloses that the output carries 'explicit caution flags for counting issues,' signalling the agent will receive warnings about continuity/absence problems rather than a bare timeline.

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?

A single dense sentence that front-loads the action, the domain, the required inputs, and the caution-flag behavior with zero filler. Nothing is repeated from the title or schema.

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?

With an output schema present, return values need not be explained, and annotations cover safety. However, for a 7-parameter tool whose optional fields drive the specificity of the answer (nationality_track, special_nationality_basis, continuity_confirmed), the description says nothing about when those matter or how this differs from sibling eligibility/visa tools.

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 71%, so the schema already documents most inputs. The description only echoes 'current status and time in Spain' (the two required params) and adds nothing about the optional nationality_track, continuity_confirmed, or qualifying_legal_residence_years fields. Baseline 3 is appropriate.

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?

Specific verb and resource: 'Explain the next permanent-residency or nationality milestone from current status and time in Spain.' An agent can tell this is a status/milestone explainer rather than a document processor. It stops short of naming which sibling it replaces (e.g., get_visa_options for pre-arrival planning), so it is clear but not sibling-differentiated.

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?

'From current status and time in Spain' implies this is for people already in Spain with an immigration status, weakly distinguishing it from the pre-arrival sibling get_visa_options. There is no explicit when-to-use, when-not-to-use, or named alternative, so usage is only implied.

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

All Spain Legal by Legal Fournier 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.

Get Residency Path

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources