Skip to main content
Glama

borbur.net salary and tax calculators

Canadian salary: the Dubai pay that matches

canada_salary_in_dubai
Read-onlyIdempotent

For a Canadian (Ontario) gross annual salary, the Dubai salary in AED that leaves the same take-home pay (no income tax in the UAE). Ontario 2026 rules, single employee. Source: https://borbur.net/tools/canada-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": {
      "cad": "<cad>"
    },
    "name": "canada_salary_in_dubai"
  }
}

Input Schema

NameRequiredDescriptionDefault
cadYesCanadian gross annual salary in Canadian dollars

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/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 genuinely useful behavioral context beyond them: the underlying tax assumption (no UAE income tax), the Ontario 2026 rule set, the single-employee assumption, and a source URL for verification.

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 sentence carries the entire purpose, conversion rule, and assumptions, with the source link trailing. Nothing is redundant and the key information is front-loaded.

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?

No output schema exists, but the description conveys what comes back (a Dubai salary in AED matching take-home pay) and pins down the assumptions that determine the number. It does not mention rounding, precision, or what happens for non-Ontario/other-filing-status inputs, which is a minor residual 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?

With one parameter at 100% schema coverage, the schema already states 'Canadian gross annual salary in Canadian dollars'. The description reinforces that the figure is gross rather than net, which matters given net-salary siblings, but adds no format, range, or unit detail beyond the schema.

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 names the specific input (Canadian Ontario gross annual salary), the specific output (Dubai salary in AED preserving take-home pay), and the conversion logic (no income tax in the UAE). The direction of conversion is unambiguous, which distinguishes it from the inverse sibling dubai_salary_in_canada without needing to name it.

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?

Applicability constraints are stated inline (Ontario 2026 rules, single employee), which helps an agent decide whether the result is relevant. However, there is no explicit when-to-use guidance and no named alternative, so an agent must infer that this is the reverse of dubai_salary_in_canada and distinct from canada_net_salary.

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