Skip to main content
Glama

Spain Legal by Legal Fournier

Check Beckham Eligibility

check_beckham_eligibility
Read-onlyIdempotent

Screen Spain's Beckham regime using qualitative gatechecks, returning the rule trace, review level, and canonical MCP resources for follow-up.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "employment_type": "<employment_type>",
      "move_reason": "<move_reason>"
    },
    "name": "check_beckham_eligibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
move_yearNoCalendar year of the relocation supporting the current article 93 entry path.
move_reasonYesMain reason for relocating to Spain.
ownership_bandNoOptional ownership context for director-style cases.
employment_typeYesEmployment structure that will support the move.
election_deadline_metNoConfirm the election deadline and required registration/evidence dates were met.
director_is_related_partyNo
relocation_link_confirmedNoConfirm the causal link and permitted timing between the qualifying activity and the move to Spain.
income_mix_requirement_metNoFor the qualifying professional branch, confirm the applicable greater-than-40-percent remuneration requirement.
spanish_tax_resident_yearsNo
prior_tax_periods_confirmedNoTrue only when the supplied tax-residence year list completely covers all five tax periods before move_year.
qualifying_activity_confirmedNoConfirm the statutory activity and exclusions: qualifying ordinary/statutory employment excluding professional sport; an eligible director appointment; an approved entrepreneur activity; or eligible startup services/training/R&D/innovation for the professional branch.
director_entity_is_patrimonialNo
years_since_last_spanish_residencyNoDeprecated elapsed-year gap; the five prior tax periods require the move year and tax-residence years.
no_disqualifying_permanent_establishmentNoConfirm no disqualifying permanent-establishment income under the applicable article 93 entry branch.

Output Schema

NameRequiredDescriptionDefault
statusYesHigh-level Beckham eligibility outcome.
reasonsYesPositive signals supporting the result.
summaryYesOne-line explanation of the result.
next_stepsYesSuggested next steps.
referencesYesSecondary Legal Fournier references.
review_levelYesHow much human review is still advisable before treating the result as filing-ready.
decision_traceYesStructured trace of the main Beckham screening factors.
blocking_issuesYesBlocking or weakening issues.
qualifying_pathsYesPotential qualifying paths.
key_rules_appliedYesStable rules applied by the tool.
related_resource_urisYesCanonical MCP resources an agent can read next without leaving the server.
official_legal_sourcesYesOfficial legal sources anchoring the Beckham analysis.
suggested_follow_up_toolsYesTool calls that are likely to advance the analysis.
current_verification_flagsYesLive-verification warnings for fact-sensitive or time-sensitive Beckham points.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
  2. Changed15 schema fields changed
    • addedInput schema / properties / director_entity_is_patrimonial
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / director_is_related_party
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / election_deadline_met
      Added value: +{
      +  "description": "Confirm the election deadline and required registration/evidence dates were met.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / income_mix_requirement_met
      Added value: +{
      +  "description": "For the qualifying professional branch, confirm the applicable greater-than-40-percent remuneration requirement.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / move_reason / enum
      Previous value: -[
      -  "new_spanish_job",
      -  "foreign_remote_work",
      -  "startup_or_innovation",
      -  "intragroup_transfer",
      -  "family_move",
      -  "other"
      -]New value: +[
      +  "new_spanish_job",
      +  "foreign_remote_work",
      +  "startup_or_innovation",
      +  "intragroup_transfer",
      +  "director_appointment",
      +  "qualifying_professional_activity",
      +  "family_move",
      +  "other"
      +]
    • addedInput schema / properties / move_year
      Added value: +{
      +  "description": "Calendar year of the relocation supporting the current article 93 entry path.",
      +  "maximum": 2100,
      +  "minimum": 2023,
      +  "type": "integer"
      +}
    • addedInput schema / properties / no_disqualifying_permanent_establishment
      Added value: +{
      +  "description": "Confirm no disqualifying permanent-establishment income under the applicable article 93 entry branch.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / prior_tax_periods_confirmed
      Added value: +{
      +  "description": "True only when the supplied tax-residence year list completely covers all five tax periods before move_year.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / qualifying_activity_confirmed
      Added value: +{
      +  "description": "Confirm the statutory activity and exclusions: qualifying ordinary/statutory employment excluding professional sport; an eligible director appointment; an approved entrepreneur activity; or eligible startup services/training/R&D/innovation for the professional branch.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / relocation_link_confirmed
      Added value: +{
      +  "description": "Confirm the causal link and permitted timing between the qualifying activity and the move to Spain.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / spanish_tax_resident_years
      Added value: +{
      +  "items": {
      +    "maximum": 2100,
      +    "minimum": 1900,
      +    "type": "integer"
      +  },
      +  "maxItems": 100,
      +  "type": "array"
      +}
    • changedInput schema / properties / years_since_last_spanish_residency / description
      Previous value: -"Number of years since the applicant was last a Spanish tax resident."New value: +"Deprecated elapsed-year gap; the five prior tax periods require the move year and tax-residence years."
    • addedInput schema / properties / years_since_last_spanish_residency / maximum
      Added value: +120
    • changedInput schema / required
      Previous value: -[
      -  "years_since_last_spanish_residency",
      -  "employment_type",
      -  "move_reason"
      -]New value: +[
      +  "employment_type",
      +  "move_reason"
      +]
    • 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"
      +]
  3. Changed1 schema field changed
    • 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"
      +]
  4. Changed1 schema field changed
    • 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"
      +]
  5. Changed1 schema field changed
    • 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"
      +]
  6. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, non-openWorld behavior, so the safety profile is covered. The description adds genuinely new behavioral context by labeling the operation 'qualitative gatechecks' and disclosing the response shape (rule trace, review level, resources), which tells the agent this is a screening advisory rather than a definitive ruling.

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 with no filler; the verb and domain come first and the output disclosure follows. It is efficiently sized, though the trailing 'canonical MCP resources for follow-up' clause is borderline boilerplate.

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?

An output schema exists, so return values need not be explained. However, for a 14-parameter tax-regime screening tool the description is thin: it does not explain how the many boolean gate flags interact, that some inputs are deprecated, or what 'review level' implies for the caller's next step.

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 79%, so the schema already carries most parameter meaning (including the deprecated note on years_since_last_spanish_residency). The description adds no parameter-level detail at all, so 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?

The description states a specific verb and resource ('Screen Spain's Beckham regime') and adds the mechanism ('qualitative gatechecks') plus the outputs (rule trace, review level, canonical MCP resources). It is clearly distinct from siblings like compare_tax_regimes or get_residency_path, though it never names an alternative.

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?

Usage is only implied: the phrase 'for follow-up' hints this is a first-pass screening step in a workflow, but there is no explicit when-to-use, when-not-to-use, or comparison against sibling tools such as compare_tax_regimes. An agent must infer the routing itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.