Skip to main content
Glama

borbur.net salary and tax calculators

Dubai salary: the Spanish gross that matches

dubai_salary_in_spain
Read-onlyIdempotent

For a monthly salary in Dubai (no income tax), the gross annual salary needed in Spain in 2026 to take home the same amount. Source: https://borbur.net/tools/dubai-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": {
      "aed_month": "<aed_month>"
    },
    "name": "dubai_salary_in_spain"
  }
}

Input Schema

NameRequiredDescriptionDefault
aed_monthYesMonthly salary in Dubai in UAE dirhams (AED)

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 readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered; the description adds genuinely useful context beyond them — the no-income-tax assumption, the 2026 tax year, and a source URL for provenance. It stops short of describing output units or whether the result is a pure calculation versus a live lookup.

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 compact sentences: the purpose and unit of the answer come first, provenance second. Nothing is repeated from the schema and no sentence is wasted.

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, the description correctly carries the return-value burden by stating the output is a gross annual Spanish salary and pinning the year to 2026. The remaining gap is that the output currency (presumably EUR) is never stated, which matters for an agent comparing or formatting 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 the single parameter is already described as 'Monthly salary in Dubai in UAE dirhams (AED)'. The description reinforces that it is a monthly Dubai figure and adds the no-income-tax context, but supplies no additional input constraints (ranges, precision, currency conversion assumptions). Baseline 3 applies when the schema carries the semantics.

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 and resource: monthly Dubai salary (AED) → required gross annual salary in Spain for 2026, with the 'no income tax' qualifier making the conversion logic legible. Directionality distinguishes it from the reverse-direction sibling (spanish_salary_in_dubai), but no sibling is named explicitly, keeping it short of a 5.

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 stated direction (you have a Dubai salary and want the Spanish equivalent), and the 'no income tax' framing signals the comparison scenario. However, there is no explicit when-to-use/when-not guidance or pointer to the reverse tool for the opposite query, so the agent must infer selection from the name and direction alone.

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