Skip to main content
Glama
chiKeka

Alberta Tax Agent

by chiKeka

Late Filing Penalty Calculator

calculate_late_penalty

Compute CRA late-filing penalties and estimated interest for T2, AT1, or GST returns. Provide unpaid tax, months late, and return type to get the amount owed.

Instructions

Calculate CRA penalties and estimated interest for late filing of T2, AT1, or GST returns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
unpaid_taxYesAmount of tax owing at the filing deadline ($)
months_lateYesNumber of complete months the return is late
return_typeNoType of returnt2
is_repeat_offenderNoFiled late in any of the 3 preceding years AND received a demand to file?
prescribed_interest_rateNoCurrent prescribed interest rate (annual, decimal)
Behavior2/5

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

With no annotations, the description carries full burden. It states the tool calculates, implying a read-only operation, but does not disclose output format, assumptions, or side effects. This is insufficient for a tool with no annotation support.

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?

The description is a single, focused sentence that front-loads the action and scope without any extraneous text.

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

Completeness2/5

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

The tool has no output schema, and the description does not explain what the calculator returns (e.g., penalty amount, interest, total). It also omits assumptions like repeat offender multipliers. This makes the description incomplete for a calculation tool.

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 description coverage is 100%, and the description adds no additional parameter context. Baseline 3 is appropriate as the schema already documents each parameter.

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 action (calculate), the resource (CRA penalties and estimated interest), and the scope (T2, AT1, or GST returns). This distinguishes it from sibling tax calculators.

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 implies use for late filing penalty calculations but provides no explicit guidance on when to choose this over alternative tax calculation tools. However, the context is unambiguous given the title and sibling set.

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/chiKeka/alberta-tax-agent'

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