Skip to main content
Glama

Spain Salary and Income Tax Calculator

Employer cost of a salary in Spain

employer_cost
Read-onlyIdempotent

What a salary in Spain costs the employer (employer social contributions itemised), or the reverse: the gross salary a total budget allows. Give gross_annual or budget_annual.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "employer_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoAge; changes the result here (young-worker reliefs, senior slabs, surcharges). Default 35.
jointNoJoint return with spouse (no income of their own) Default false.
regionNoRegion. Basque Country and Navarre run their own tax systems and are not covered.: madrid = Madrid; catalonia = Catalonia (Barcelona); andalusia = Andalusia (Málaga, Seville); valencia = Valencia (Alicante). Default madrid.
beckhamNoBeckham regime (inbound worker). Flat 24% on Spanish employment income up to €600,000 for six years. Default false.
marriedNoMarried or registered partner. Default false.
childrenNoNumber of dependent children. Default 0.
bonus_annualNoYearly bonus in EUR. Default 0.
gross_annualNoGross yearly salary in EUR
budget_annualNoTotal yearly employer budget in EUR, to find the gross salary it allows
spouse_incomeNoPartner's gross yearly income in EUR, for joint taxation and spouse allowances. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds that results itemise employer social contributions, which is useful given there is no output schema, but it stays silent on calculation assumptions, regional tax-system limits, or how conflicting inputs are handled.

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?

Two sentences, front-loaded with the core definition and ending with the actionable input instruction. No filler, no restatement of the title.

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 10-parameter calculator with full schema coverage but no output schema, the description covers purpose, both directions, and result content. The main remaining gap is that it never states the exclusivity rule explicitly or what the tool does when both gross_annual and budget_annual are missing.

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?

Schema coverage is 100%, so the baseline is 3. The description goes beyond the schema by framing gross_annual and budget_annual as mutually exclusive alternatives ('or'), which the schema does not convey since both are optional with zero required parameters.

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 names a specific resource and metric (employer cost of a salary in Spain) and explicitly covers both directions of the calculation, including itemised employer social contributions. It does not explicitly distinguish itself from siblings like net_salary or gross_for_target_net, so an agent must infer the boundary.

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 closing instruction 'Give gross_annual or budget_annual' tells the agent how to pick between the two operating modes, which is real usage guidance. However, it never says when to choose this tool over net_salary or gross_for_target_net, nor what happens if neither mode parameter is supplied.

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