Skip to main content
Glama

borbur.net salary and tax calculators

Dubai salary: the Canadian pay that matches

dubai_salary_in_canada
Read-onlyIdempotent

For a monthly Dubai salary in AED (tax-free), the gross annual salary needed in Ontario, Canada, in 2026 to take home the same. Source: https://borbur.net/tools/dubai-salary-in-canada/

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

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.7/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 substantive context beyond that: the calculation targets Ontario specifically, pins the tax year to 2026, and states the input is tax-free while the output is a gross figure. That clarification of gross-vs-net and jurisdiction is real behavioral value.

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 states the input, the target jurisdiction, the year and the output basis, with no padding. The trailing source URL is mildly extraneous to an agent's decision but short enough not to distract.

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 calculator with no output schema, the description covers what is needed: the input units, the assumption of tax-free Dubai pay, the Ontario jurisdiction and the 2026 tax year. Only the return format (single annual figure? currency?) is left implicit, which is a minor gap.

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 description coverage is 100% and the single parameter already documents 'Monthly salary in Dubai in UAE dirhams (AED)'. The description repeats the monthly-AED framing but adds no unit conversion details, rounding behavior, or bounds. Baseline 3 is appropriate 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?

The description names a precise transformation: take a monthly AED salary in Dubai and produce the equivalent gross annual salary in Ontario for 2026. That is a specific verb+resource statement an agent can act on. It does not explicitly distinguish itself from the inverse sibling 'canada_salary_in_dubai', leaving the directionality to be inferred from the phrasing.

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 only implied by the opening phrase 'For a monthly Dubai salary in AED (tax-free)', which signals the required input condition. There is no statement of when-not to use it and no reference to the reverse-direction tool that likely exists among the siblings. An agent must infer the appropriate scenario.

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