Skip to main content
Glama

borbur.net salary and tax calculators

Spain Beckham Law vs normal tax 2026

spain_beckham_law
Read-onlyIdempotent

Compares take-home pay in Spain in 2026 under the Beckham Law special regime for people moving to Spain (24% flat up to EUR 600,000, 47% above) and under the normal income tax regime, for a gross annual employment salary. Source: https://borbur.net/tools/beckham-law-calculator/

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": {
      "gross": "<gross>"
    },
    "name": "spain_beckham_law"
  }
}

Input Schema

NameRequiredDescriptionDefault
grossYesGross annual salary in euros

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds real substance beyond that: the two regimes being contrasted, the exact flat-rate brackets, the 2026 tax year, the input assumption (employment income only) and a source URL for provenance. It does not say what the output looks like (breakdown, currency, whether social security is included), which keeps it from a 5.

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?

One dense sentence that front-loads the comparison being performed, then the rates, then the input scope, with the source URL trailing. No filler or redundant restatement of the tool name.

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 one-parameter, read-only calculator with no output schema, the definition supplies enough to call it correctly: what is compared, the tax year, the brackets and the input assumption. The only gap is that the shape of the result (two take-home figures, effective rate, currency formatting) is left implicit.

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?

There is a single parameter with 100% schema description coverage, so the schema already defines 'gross' as the gross annual salary in euros. The description restates this as 'gross annual employment salary', adding only the employment-income qualifier, which is a marginal gain over structured data.

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 names a specific computation: a comparison of take-home pay in Spain for 2026 under the Beckham Law regime versus the normal income tax regime, including the rate brackets (24% up to EUR 600,000, 47% above). The qualifier 'for people moving to Spain' and 'gross annual employment salary' distinguishes it from a plain net-salary sibling such as spain_net_salary.

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

Usage Guidelines4/5

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

It clearly states the applicable context: a person relocating to Spain, with a gross annual employment salary, wanting a regime comparison for 2026. It does not name alternatives or state when not to use it (e.g., for existing residents already on the normal regime), so it stops short of explicit routing guidance.

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.

Resources