Spain Legal by Legal Fournier

Find Legal Fournier Tool

find_legal_fournier_tool

Read-onlyIdempotent

Match a Spain legal, tax, property, business, or private-client case to the best Legal Fournier public tool page and MCP workflow.

Input Schema

TableJSON Schema

Name	Required	Description
`area`	No	Optional broad area when the agent already knows it.
`query`	No	Natural-language user goal or case summary, such as 'high-income founder buying property in Spain'.
`max_results`	No	Maximum number of matched public tools to return when include_all_tools is false.
`include_all_tools`	No	Return the full Legal Fournier public tool catalog instead of only top matches.
`complexity_signals`	No	Signals that should affect matching and escalation.
`preferred_language`	No	Preferred public-page language when an equivalent translated tool exists.

Output Schema

TableJSON Schema

Name	Required	Description
`handoff_url`	Yes	Site-controlled consultation handoff URL.
`catalog_size`	Yes	Number of public Legal Fournier tools in the MCP catalog.
`legal_notice`	Yes	General legal notice that agents must preserve when using tool results.
`next_actions`	Yes	Immediate actions for the agent after matching the public tool.
`matched_tools`	Yes	Ranked public tools and their agent workflow guidance.
`query_summary`	Yes	Short summary of the matching inputs and result count.
`agent_use_rules`	Yes	Rules for agents using the public tools with MCP outputs.
`catalog_resource_uri`	Yes	Canonical MCP resource URI for the complete public tool catalog.
`recommended_mcp_sequence`	Yes	Recommended MCP tool sequence before the public-page or human handoff.

TDQS

A3.7/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds context about the scope (Spain legal/tax/property/business/private-client) and output (public tool page and MCP workflow), but does not disclose matching logic, ranking criteria, or ambiguous query behavior. It does not contradict annotations.

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?

The description is a single sentence of 24 words, front-loaded with the core action ('Match') and resource, with no redundant or filler content. Every word contributes to the meaning.

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?

Given the tool's routing purpose, the description states its function and scope but does not explain when to use it versus siblings or what kind of output to expect beyond 'public tool page and MCP workflow'. The rich schema and annotations reduce the burden, but the description still lacks explicit usage context. It is minimally complete.

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%, with all six parameters documented in the input schema, including enums for 'area' and 'preferred_language'. The description adds no additional parameter-level meaning beyond the schema, so the baseline of 3 is appropriate.

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?

The description uses a specific verb ('Match') with a clear resource ('a Spain legal, tax, property, business, or private-client case') and target ('best Legal Fournier public tool page and MCP workflow'). It clearly distinguishes this from sibling tools like check_beckham_eligibility or compare_tax_regimes, which are domain-specific, by positioning this as a routing/matching tool.

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?

The description implies a usage scenario (when you have a legal case and need to find the right tool), but it does not explicitly state when to prefer this over directly using a specific sibling tool. There are no exclusions or alternatives mentioned, so guidance is only implicit.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

Most tools have distinct purposes, but get_paid_call_availability and get_paid_consultation_options overlap somewhat: one reads live availability for the 45-minute call while the other covers broader consultation options including that same call. This minor overlap is manageable given the clear descriptions.

Naming Consistency4/5

Naming follows a consistent verb_noun pattern (check_, compare_, create_, explain_, get_, route_, run_) with only minor deviations like the verbose 'create_legal_fournier_contact_request' and the slightly odd 'get_paid_call_availability'. Overall readable and predictable.

Tool Count5/5

The 11 tools are well-scoped for a Spain legal advisory server, covering eligibility, comparison, process explanation, visa/residency guidance, and client engagement. This is an appropriate size that avoids bloat while providing a complete service.

Completeness4/5

The tool set covers the core domain well: Beckham regime checks, tax comparison, NIE process, visa/residency guidance, and Legal Fournier consultation/contact flows. Missing are transactional tools like booking directly or tracking requests, but the paid consultation options provide endpoints for those actions, so agents can work around gaps.

Resources

Need Help?