Spain Legal by Legal Fournier

Get Visa Options

get_visa_options

Read-onlyIdempotent

Rank Spain residence routes using evergreen logic and return decision traces, next actions, and canonical MCP resources for the leading branches.

Input Schema

Name	Required	Description
`intent`	Yes	Main relocation intent.
`nationality`	Yes	Applicant nationality as a country name or ISO-style country code.
`income_source`	Yes	Main source of income for the move.
`employer_location`	No	Where the main employer or client base is located, if known.
`has_eu_family_link`	No	Whether an EU family-member route may need separate review.
`investment_profile`	No	Whether the investment plan is passive or tied to an operating business.
`sponsor_nationality`	No
`has_spanish_job_offer`	No	Whether the applicant already has a Spanish job offer.
`eu_family_relationship`	No	Optional relationship label when an EU-family route may be relevant.
`sponsor_exercised_free_movement`	No

Output Schema

Name	Required	Description
`references`	Yes	Secondary Legal Fournier references, demoted behind MCP-native context.
`next_actions`	Yes	Next actions to progress the analysis.
`review_level`	Yes	How much human review is still advisable before treating the result as filing-ready.
`general_notes`	Yes	General notes that apply across the route list.
`ranked_routes`	Yes	Ranked visa or residence routes.
`decision_trace`	Yes	Structured trace of the main route-selection factors.
`profile_summary`	Yes	One-line summary of the screened profile.
`ruled_out_routes`	Yes	Common routes ruled out by stable legal logic.
`key_rules_applied`	Yes	Stable rules that drove the recommendation.
`related_resource_uris`	Yes	Canonical MCP resources an agent can read next without leaving the server.
`official_legal_sources`	Yes	Official legal sources that anchor the recommendation.
`suggested_follow_up_tools`	Yes	Tool calls that are likely to advance the analysis.
`current_verification_flags`	Yes	Live-verification warnings for volatile or fact-sensitive points.
`nationality_classification`	Yes	High-level nationality bucket used by the route logic.

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"

Changed6 schema fields changedOct 18, 2026

addedInput schema / properties / nationality / maxLength
```
Added value: +100
```
addedInput schema / properties / nationality / minLength
```
Added value: +1
```
addedInput schema / properties / sponsor_exercised_free_movement
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / sponsor_nationality

Added value: +{
+  "maxLength": 100,
+  "minLength": 1,
+  "type": "string"
+}

changedOutput schema / properties / nationality_classification / enum

Previous value: -[
-  "eu_eea_swiss",
-  "non_eu"
-]New value: +[
+  "eu_eea_swiss",
+  "non_eu",
+  "spanish",
+  "unknown"
+]

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

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds that it ranks branches using 'evergreen logic' and emits decision traces/next actions, which is meaningful behavioral context, but it says nothing about how ranking is scoped or what disqualifies a route.

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?

A single front-loaded sentence that leads with the core action and then the outputs; there is no wasted filler. It leans on jargon ('evergreen logic', 'canonical MCP resources') that costs some readability but not length.

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 carry the safety profile. But for a 10-parameter tool with 5 enums and intent-dependent optional params, the description gives no sense of which inputs gate which routes, leaving the agent to reverse-engineer that from the schema.

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 coverage is 80%, so the flat params are largely documented by the schema itself, and the 5 enums are self-describing. The description adds no parameter meaning beyond the schema and does not clarify the conditional relationship between intent, income_source, and the sponsor/investment params.

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?

States a specific verb (Rank) and resource (Spain residence routes), and discloses outputs (decision traces, next actions, resources). However, it never distinguishes itself from overlapping siblings like get_residency_path or check_beckham_eligibility, so an agent must guess which route tool applies.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no alternatives named despite several sibling tools (get_residency_path, check_beckham_eligibility, compare_tax_regimes) that plausibly overlap. The agent is left to infer the routing condition entirely.

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 Visa Options

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources