Skip to main content
Glama

borbur.net salary and tax calculators

Spain net salary 2026

spain_net_salary
Read-onlyIdempotent

Net (take-home) pay in Spain in 2026 from a gross annual salary, using the official AEAT withholding algorithm and 2026 Social Security rates. Single employee, no children, under 65, permanent contract. Returns Social Security, withholding rate, withholding and net per year and per month (12 or 14 payments). Source: https://borbur.net/tools/spain-net-salary-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_net_salary"
  }
}

Input Schema

NameRequiredDescriptionDefault
grossYesGross annual salary in euros (e.g. 50000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world behavior, and the description adds genuinely useful context beyond them: the imposed scenario constraints (single, no children, under 65, permanent contract) and what the output contains. The main unaddressed point is how the 12- versus 14-payment split is chosen, since no parameter controls it.

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?

Two dense sentences, front-loaded with purpose and followed by constraints, outputs, and source. Almost every clause earns its place; the source URL is the only slightly extraneous element.

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 calculator with no output schema, the description covers inputs, assumptions, and the shape of the return (Social Security, withholding rate, withholding, net, yearly and monthly). The unexplained 12/14 payment selection is the one loose end.

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 100% and the single parameter already documents 'Gross annual salary in euros' with an example, so the description adds nothing beyond reaffirming annual gross. With fully covered schema this is the baseline.

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 uses a precise verb+resource ('Net (take-home) pay in Spain in 2026 from a gross annual salary') and pins down the calculation basis (AEAT withholding algorithm, 2026 Social Security rates). It does not name a sibling to contrast with, so an agent must infer from the stated assumptions (single, no children, under 65) that this is the default case rather than e.g. spain_beckham_law.

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 eligibility assumptions imply the usage context, but there is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as the Beckham law variant. An agent gets an implied fit but is left to reason about whether a caller's situation matches.

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