Skip to main content
Glama

borbur.net salary and tax calculators

Spanish salary: the US pay that matches

spanish_salary_in_the_us
Read-onlyIdempotent

For a gross annual salary in Spain, the US salary that leaves the same take-home pay in a state with no income tax. Source: https://borbur.net/tools/spanish-salary-in-the-us/

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_us"
  }
}

Input Schema

NameRequiredDescriptionDefault
grossYesGross annual salary in Spain in euros

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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 one genuinely useful behavioral fact — the result assumes a state with zero income tax, so it is not valid for states that levy tax — but says nothing about rounding, estimate precision, or the output currency, which matter for a pay-equivalence calculation.

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?

One front-loaded sentence plus a source link — no padding. The phrasing is a noun fragment rather than a full clause ('the US salary that leaves...'), which is compact and readable, though slightly less crisp than a direct verb statement.

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?

With no output schema and a single documented input, the description is nearly complete: it says what comes back (a US salary) and the key modeling assumption (no state income tax). Only the output currency and the estimate/rounding nature of the figure are left implicit.

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?

Single parameter with 100% schema coverage; the schema already says gross annual salary in Spain in euros. The description restates the same framing but adds no unit, range, or boundary guidance beyond it, so the 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 verb-less but unambiguous transformation: given a gross annual salary in Spain, return the matching US salary preserving take-home pay. It names the concrete constraint (a state with no income tax), which distinguishes it from the ordinary conversion siblings, though it never names the inverse tool us_salary_in_spain 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?

The directional framing implies when to use it (Spain → US comparison), but there is no explicit when-to-use/when-not guidance and no pointer to the reverse or net-salary siblings which an agent might otherwise pick. Usage is inferable rather than stated.

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