Skip to main content
Glama

borbur.net salary and tax calculators

Spanish salary: the Dubai pay that matches

spanish_salary_in_dubai
Read-onlyIdempotent

For a gross annual salary in Spain, the monthly Dubai salary (AED) that leaves the same take-home pay, and how much more is kept if the same gross is paid in Dubai. Source: https://borbur.net/tools/spanish-salary-in-dubai/

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

Input Schema

NameRequiredDescriptionDefault
grossYesGross annual salary in Spain in euros

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 the safety profile is covered. The description adds real behavioral value by disclosing both return components (monthly AED equivalent and the extra amount kept) and citing a source for the calculation, which matters since no output schema exists.

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 delivers the input, both outputs, and the currency; the source URL is tacked on at the end without disrupting flow. No redundant 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 single-parameter calculation tool with no output schema, the description adequately explains what comes back (two figures, one in AED). Minor gaps remain, such as whether the take-home comparison assumes any specific assumptions or the exact return shape, but nothing essential to correct invocation is missing.

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's description ('Gross annual salary in Spain in euros') already matches the tool description's phrasing. The description adds essentially no format, range, or unit detail beyond what the schema states.

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?

The description states a specific computation: given a gross annual salary in Spain, return the monthly Dubai salary in AED that preserves take-home pay, plus the extra amount kept. The Spain→Dubai direction is explicit, so an agent can distinguish it from siblings like spanish_salary_in_the_uk or canada_salary_in_dubai without opening 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 input framing ('For a gross annual salary in Spain') and the Dubai output make the applicable scenario unambiguous, so the agent knows exactly when this tool fits. What's missing is an explicit exclusion or an alternative named for other country pairs, though the directional wording effectively serves that role.

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