Skip to main content
Glama

borbur.net salary and tax calculators

UK salary: the Spanish gross that matches

uk_salary_in_spain
Read-onlyIdempotent

For a UK gross annual salary, the gross salary needed in Spain in 2026 to take home the same (UK 2026/27 income tax + NI; Spain single, no children). Source: https://borbur.net/tools/uk-salary-in-spain/

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": {
      "gbp": "<gbp>"
    },
    "name": "uk_salary_in_spain"
  }
}

Input Schema

NameRequiredDescriptionDefault
gbpYesUK gross annual salary in pounds

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered. The description adds real value beyond that by disclosing the modelling assumptions: UK 2026/27 income tax plus NI on one side, and a Spain single-filer, no-children scenario on the other, plus a source URL for provenance.

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?

A single dense sentence plus a source link. The input scope and comparison basis are front-loaded, and nothing is wasted or repeated.

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 lookup with no output schema, the key modelling assumptions and provenance are present. The one gap is that the output currency/units of the Spanish figure are not stated, which matters for an agent reporting the result.

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 there is only one parameter, already documented as the UK gross annual salary in pounds. The description restates the same input without adding format, range, or rounding guidance, so baseline 3 applies.

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?

States a specific computed quantity and an explicit direction of conversion: a UK gross salary mapped to the Spanish gross that yields the same take-home pay in 2026. The directionality distinguishes it from reverse siblings such as spanish_salary_in_the_uk, though no sibling is named explicitly.

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 implied by the tight scope (UK gross in, Spain gross out) rather than stated. There is no explicit when-to-use/when-not guidance and no pointer to complementary tools like spain_net_salary or spanish_salary_in_the_uk for the inverse direction.

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