Skip to main content
Glama

borbur.net salary and tax calculators

Spanish salary: the UK pay that matches

spanish_salary_in_the_uk
Read-onlyIdempotent

For a Spanish gross annual salary in euros, the UK salary that leaves the same take-home pay (Spain 2026; UK 2026/27 income tax + NI, England, Wales, Northern Ireland). Source: https://borbur.net/tools/spanish-salary-in-the-uk/

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": "spanish_salary_in_the_uk"
  }
}

Input Schema

NameRequiredDescriptionDefault
grossYesGross annual salary in Spain in euros

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, closed-world), so the description only needs to add calculation context — and it does, disclosing the tax years, the assumed UK sub-jurisdictions, and a source URL for the underlying rules. It does not disclose output shape (gross UK figure?), rounding, or whether allowances/benefits are modelled, so the extra context is useful but partial.

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 front-loaded sentence conveys the input, the output, and the equivalence criterion, followed by the assumption set and a source. No redundant phrasing and nothing an agent must read past to understand the operation.

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 single-parameter deterministic calculator with no output schema, the description says enough: what goes in, what comes out, which tax rules apply, and where they come from. Minor gaps remain around output formatting and handling of non-England/Wales/NI (Scottish) salaries, but nothing blocking.

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% and the single parameter already documents 'Gross annual salary in Spain in euros'; the description restates exactly that with no added syntax, ranges, or edge-case guidance. Baseline 3 is appropriate since the schema carries the full burden.

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?

States a precise transformation: given a Spanish gross annual salary in euros, return the UK salary yielding the same take-home pay. The direction (Spain in, UK out) plus the named tax regimes (Spain 2026; UK 2026/27 income tax + NI, England, Wales, Northern Ireland) let an agent distinguish this from inverse siblings like uk_salary_in_spain and from other destination siblings without inspecting any schema.

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?

The equivalence basis (take-home parity) and the exact jurisdiction/year scope are stated, which implicitly tells the agent this is for Spain-to-UK purchasing-power/net-pay comparisons in the 2026/27 UK regime, and excludes Scottish taxpayers by naming only England, Wales and Northern Ireland. It stops short of explicitly naming an alternative tool or a when-not-to-use case (e.g., that reverse conversions belong to uk_salary_in_spain).

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