Skip to main content
Glama
tresor4k

macalc

by tresor4k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

calculate_canada_federal_tax

Read-onlyIdempotent

Estimate Canadian federal income tax using CRA brackets and basic personal amount. Enter annual income to compute taxable income, federal tax, and effective/marginal rates.

Instructions

Calculate Canadian FEDERAL income tax using CRA brackets and the basic personal amount. Use for a federal-only estimate; provincial/territorial tax and CPP/EI are NOT included, so the real total tax is higher. Input: income_cad (annual income in CAD). Returns basic personal amount, taxable income, federal tax, effective and marginal rates. Read-only, deterministic, estimate only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
income_cadYesAnnual income in Canadian dollars (CAD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "formula": {
-      "description": "Human-readable formula or method used (e.g. \"I=P·r·t\", \"Magnus formula\").",
-      "type": "string"
-    },
-    "reference_url": {
-      "description": "Link to a calcul2 page documenting the calculation in detail.",
-      "type": "string"
-    },
-    "result": {
-      "description": "Computed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools)."
-    },
-    "source": {
-      "description": "Authoritative source for the rule or formula (e.g. \"Article 197 CGI\", \"NF DTU 21\").",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. Changed1 schema field changedv0.1.4
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "formula": {
+      "description": "Human-readable formula or method used (e.g. \"I=P·r·t\", \"Magnus formula\").",
+      "type": "string"
+    },
+    "reference_url": {
+      "description": "Link to a calcul2 page documenting the calculation in detail.",
+      "type": "string"
+    },
+    "result": {
+      "description": "Computed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools)."
+    },
+    "source": {
+      "description": "Authoritative source for the rule or formula (e.g. \"Article 197 CGI\", \"NF DTU 21\").",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. Addedv0.1.1

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare readOnlyHint, idempotentHint, and destructiveHint. The description adds 'deterministic' and 'estimate only', and lists the output fields (basic personal amount, taxable income, federal tax, effective and marginal rates). No contradiction with annotations.

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?

Three sentences, front-loaded with purpose, then usage guidelines, then input/output summary. No redundant information; every sentence adds value.

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?

For a simple single-parameter tool with no output schema, the description covers purpose, inclusions/exclusions, input format, and output fields. It is complete and leaves no ambiguity.

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% with a single parameter described as 'Annual income in Canadian dollars (CAD)'. The description repeats this information without adding extra semantics. Baseline 3 is appropriate as schema does the heavy lifting.

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 it calculates Canadian federal income tax using CRA brackets and basic personal amount, and distinguishes from siblings by specifying it is federal-only and excludes provincial tax and CPP/EI. The verb 'calculate' and resource are specific.

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?

The description explicitly says to use for a federal-only estimate and notes what is not included (provincial tax, CPP/EI) and that the real total is higher. While it does not name alternative tools among siblings, it provides good context on when to use and limitations.

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

Deploy Server

Other Tools