Skip to main content
Glama

Canada Payroll — employer cost & take-home math (2026)

by ca.canada-payroll

employee_take_home

2026 take-home pay for a Canadian employee on regular salary: CPP/QPP (incl. second-ceiling CPP2/QPP2), EI (and QPIP for Quebec), federal and provincial income tax withheld, net pay per year and per pay period. Assumes a full-year employee with basic TD1 claims. Supported: all 13 Canadian provinces/territories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
provinceYesTwo-letter province/territory code
annual_salaryYesGross annual salary, CAD
pay_frequencyNoPay frequency for the per-period view (default biweekly)

TDQS

A4.5/5.0
Behavior4/5

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

No annotations provided, so description handles transparency. Discloses deductions, assumptions, and year (2026). No side effects; it's a calculation tool.

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 sentences with no wasted words. Front-loaded with purpose, then assumptions. Highly efficient.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, but description explains return values (net per year and per period). Assumptions and coverage are sufficient for a calculation tool with no annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all 3 params (100%). Description adds value by connecting parameters to deductions and output frequencies, enhancing meaning beyond 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 clearly states the tool computes take-home pay for Canadian employees, listing specific deductions (CPP/QPP, EI, QPIP, taxes) and outputs (net per year and per period). Siblings are employer_cost and net_to_gross, making this distinct.

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?

Explicitly states assumptions (full-year employee, basic TD1 claims) and coverage (all 13 provinces). No when-not-to or alternatives, but context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Canada Payroll — employer cost & take-home math (2026) toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool addresses a distinct payroll question: employee take-home, employer total cost, and net-to-gross inversion. No two tools overlap in purpose.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (employee_take_home, employer_total_cost, net_to_gross_salary), making the set predictable.

Tool Count4/5

With only 3 tools, the server is tightly scoped to payroll calculations. While more specialized tools could be added, the count matches the narrow domain.

Completeness4/5

The tool set covers the core payroll math: net pay, employer cost, and conversion. Minor gaps exist (e.g., no tool for adjusting TD1 claims), but the primary workflows are supported.

Resources