Skip to main content
Glama

borbur.net salary and tax calculators

Canada take-home pay 2026 (Ontario)

canada_net_salary
Read-onlyIdempotent

Canadian take-home pay in 2026 in Ontario for a single employee: federal and Ontario income tax (with the Ontario surtax and Health Premium), CPP, CPP2 and Employment Insurance. 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": {
      "gross": "<gross>"
    },
    "name": "canada_net_salary"
  }
}

Input Schema

NameRequiredDescriptionDefault
grossYesGross annual salary in Canadian dollars

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description usefully adds which statutory components are included (Ontario surtax, Health Premium, CPP2), but says nothing about the shape of the result or the underlying assumptions beyond 'single employee'.

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 dense, front-loaded sentence states scope, followed by a short source citation. Nothing is redundant, though the trailing URL is of marginal operational value to an agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 is the only signal about results; listing the included deductions partially covers that, but it never states whether the output is an annual net figure, a per-period figure, or a full breakdown. For a one-parameter read-only calculator this is adequate but leaves a real 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 coverage is 100% and the single parameter is already documented as 'Gross annual salary in Canadian dollars'. The description reinforces the annual gross basis and the no-dependents assumption but adds no formatting or edge-case guidance (e.g., zero income, part-year).

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 the exact computation (take-home pay), the jurisdiction and tax year (Canada/Ontario, 2026), and the filer profile (single employee), and it enumerates the deductions modeled. That is far more specific than a restated title, though it never explicitly contrasts itself with siblings such as canada_salary_in_dubai.

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 is only implied through scope qualifiers ('single employee', 'Ontario', '2026'), which implicitly exclude married filers, other provinces, and other years. There is no explicit when-to-use statement and no named alternative for cases outside that scope.

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