Skip to main content
Glama
UseCOS MCP Server

UseCOS MCP Server

by rivlosys

calculate_canadian_paycheck

Calculate Canadian take-home pay from gross income, including federal and provincial tax, CPP/CPP2, EI/QPIP, and Ontario surtax across all provinces and territories.

Instructions

Calculate Canadian take-home pay, federal/provincial income tax, CPP/CPP2, EI/QPIP, and Ontario surtax across all 13 provinces and territories.

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": {
      "amount": "<amount>"
    },
    "name": "calculate_canadian_paycheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesGross employment income for the selected period in CAD
periodNoannual
provinceNoON
retirementRRSPNoAnnual RRSP deduction in CAD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It says what is computed but not that results are estimates based on a specific (unstated) tax year's rate tables, nor anything about rounding, precision, or the fact that the answer is a static approximation rather than authoritative tax advice. For a financial calculation tool that silently embeds year-specific rates, omitting the tax year is a material gap.

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?

A single dense sentence with the core purpose front-loaded and no filler. The acronym list (CPP2, QPIP) is efficient for a domain audience but does not explain them, which is acceptable given the tool's narrow remit.

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 four parameters, no annotations, and no output schema, the description should say more than it does. It never states the tax year or rate assumption, the shape of the result (a breakdown of net pay and deductions?), or how the annual-only RRSP deduction interacts with monthly/weekly periods. Adequate to select the tool, insufficient to predict its output.

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 50%: amount and retirementRRSP are documented in the schema, while period and province are bare enums with defaults. The description partially compensates by signalling that all 13 provinces/territories are supported and that jurisdiction drives federal/provincial and QPIP treatment, but it never explains that amount is interpreted per period, nor what the period choices mean for the output.

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?

Uses a specific verb (Calculate) with a precisely scoped resource (Canadian take-home pay) and enumerates the exact components computed: federal/provincial tax, CPP/CPP2, EI/QPIP, Ontario surtax. The pay/tax-deduction scope is clearly distinct from the sibling tools (auto loan, GST/HST, mortgage, VIN validation), so an agent can route without reading the schema.

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 domain: use this when you need net pay from gross employment income. There is no statement of when to prefer this over the loan/GST siblings, no preconditions such as which tax year or employment type the tables reflect, and no exclusions (e.g. self-employment, non-employment income).

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