Skip to main content
Glama
tresor4k

macalc

calculate_canada_combined_tax

Calculate combined Quebec federal income tax including the 16.5% Quebec abatement. Returns provincial, federal gross/net, and total taxes for a given income.

Instructions

Calculate combined Quebec + federal income tax with the Quebec federal abatement (16.5%). Returns: {income_cad, quebec_provincial_tax, federal_gross_tax, federal_abatement_qc, federal_net_tax, total_combined_tax, ...}. See list_bundles for related 'finance-afrique-quebec' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
income_cadYesAnnual income in CAD

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior4/5

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

Discloses the return fields in the output, including the abatement percentage. However, no annotations are provided, so the description carries the full burden; it is fairly transparent for a calculator 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, front-loaded with the action, and includes a useful reference to related tools. Every sentence adds value.

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?

Given the simplicity of the tool (one parameter, no annotations, output schema exists), the description is relatively complete, showing output fields and a reference to related calculators.

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 parameter description is adequate. The tool description adds no extra meaning beyond the schema's description of income_cad.

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?

Clearly states the tool calculates combined Quebec and federal income tax with the abatement, but does not explicitly differentiate from sibling tools like calculate_quebec_income_tax or calculate_canada_federal_tax.

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?

Provides a reference to list_bundles for related calculators, but lacks explicit guidance on when to use this tool versus alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/macalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server