Skip to main content
Glama

borbur.net salary and tax calculators

US salary: the Spanish gross that matches

us_salary_in_spain
Read-onlyIdempotent

For a US gross annual salary, the gross salary needed in Spain in 2026 to take home the same (US federal tax + FICA, no state tax; Spain single, no children). Source: https://borbur.net/tools/us-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": {
      "usd": "<usd>"
    },
    "name": "us_salary_in_spain"
  }
}

Input Schema

NameRequiredDescriptionDefault
usdYesUS gross annual salary in dollars

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 establish read-only, idempotent, closed-world behavior, so the description adds meaningful behavioral context by disclosing tax assumptions, filing status, dependents, and year. It does not state the output currency or format, but that gap is modest given there is no output schema.

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?

The purpose and key assumptions are packed into one front-loaded sentence, followed by a compact source URL. There is no redundant or filler wording.

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 calculation tool with no output schema, the definition supplies the important non-obvious context: year, tax assumptions, filing status, dependents, and source. It could explicitly state the output currency, but it is otherwise sufficient for correct invocation.

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?

The single usd parameter is fully documented in the schema as the US gross annual salary in dollars. The description adds no further parameter meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 computation: a US gross annual salary is converted into the Spanish gross needed in 2026 to match take-home pay, with tax assumptions. The direction and scope distinguish it from reverse-direction siblings such as spanish_salary_in_the_us, though no sibling is explicitly named.

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?

Gives applicable context such as US federal tax plus FICA, no state tax, Spain single, no children, and 2026. However, it does not explicitly say when to use this versus reverse-direction or other-country siblings, nor when not to use it.

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