Spain Legal by Legal Fournier

Explain NIE Process

explain_nie_process

Read-onlyIdempotent

Return the stable NIE and TIE workflow, the key procedural distinctions, and the canonical process resource for agents.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`forms`	Yes	Relevant forms and administrative references.
`steps`	Yes	Ordered process steps.
`summary`	Yes	Short overview of the NIE/TIE process.
`references`	Yes	Secondary Legal Fournier references.
`next_actions`	Yes	Next actions to progress the procedure.
`review_level`	Yes	How much human review is still advisable before treating the result as filing-ready.
`decision_trace`	Yes	Structured trace of the procedural distinctions that matter.
`common_mistakes`	Yes	Common mistakes in NIE/TIE processing.
`key_distinctions`	Yes	Key distinctions that agents should preserve.
`key_rules_applied`	Yes	Stable procedural rules applied by the tool.
`related_resource_uris`	Yes	Canonical MCP resources an agent can read next without leaving the server.
`official_legal_sources`	Yes	Official legal and administrative sources anchoring the procedure.
`suggested_follow_up_tools`	Yes	Tool calls that are likely to advance the analysis.
`current_verification_flags`	Yes	Live-verification warnings for office-level or fee-level volatility.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026

changedOutput schema / $schema

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

Changed1 schema field changedOct 18, 2026

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

Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world. The description repeats output content but adds no behavioral context such as auth requirements, rate limits, or side effects. With an output schema present, return value details are redundant.

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?

Single sentence, front-loaded with the action and returned items. Minor jargon but no wasted words.

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 no-param read-only tool with an output schema and full annotations, the description adequately states what it returns. It lacks usage context, but that is covered in another dimension.

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?

Zero parameters, so baseline is 4. The description need not address parameters, and the schema is empty.

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 'Return' and specific resources 'NIE and TIE workflow' and 'canonical process resource'. Distinguishes from siblings by focusing on process explanation, though it doesn't name alternative tools.

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?

No explicit when-to-use, when-not, or alternative tools. The only hint is 'for agents', which is not actionable usage guidance.

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.

Explain NIE Process

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources