Skip to main content
Glama

FreelancerTax — Canadian self-employed tax math

gst_quick_method_compare

Compare the GST/HST Quick Method against the regular method for a Canadian small business: eligibility (revenue ceiling + excluded professions), remittance under each method, and which one keeps more money. Annual figures.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
revenueYesAnnual taxable revenue BEFORE tax, CAD
provinceYesTwo-letter province code of the permanent establishment (e.g. ON, BC, QC)
business_typeNoFree-text business type, e.g. 'services', 'consultant', 'retail goods', 'bookkeeper' (used for the excluded-professions test; goods vs services rate)
itc_eligible_expenses_incl_taxNoAnnual ITC-eligible operating expenses INCLUDING tax, CAD (for the regular-method comparison)

TDQS

A3.9/5.0
Behavior3/5

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

No annotations provided, so description bears full burden. It implies a read-only calculation (comparison) but does not explicitly state no side effects, data modification risks, or authentication needs. Adequate for a non-destructive tool but lacking explicit safety disclosure.

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?

Single, well-structured sentence that front-loads the main action and covers key aspects without redundancy. Every word earns its place.

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?

Given no output schema, the description lacks details about the comparison output format, constraints, or error handling. Adequate for a simple tool but leaves some gaps in expected return value.

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%, so baseline 3. The description adds high-level context (e.g., 'revenue ceiling', 'excluded professions') but does not provide additional parameter-specific details beyond what the schema already offers.

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's purpose: comparing GST/HST Quick Method to the regular method, covering eligibility, remittance, and financial comparison. It distinguishes from sibling tools like registration or deadline checks.

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 context is clear: it's for comparing two tax methods for Canadian small businesses. However, it does not explicitly state when not to use or list alternatives, though sibling context provides differentiation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool addresses a distinct aspect of Canadian self-employed tax: CPP contributions, full tax estimate, deadlines, GST registration, GST method comparison, and instalment plans. No overlap in functionality.

Naming Consistency4/5

All names use lowercase with underscores, making them readable. However, they mix verb-noun patterns (e.g., get_tax_deadlines, estimate_self_employed_tax) with noun phrases (cpp_self_employed, instalment_plan), showing minor inconsistency from the ideal verb_noun standard.

Tool Count5/5

Six tools is a well-scoped number for the domain. Each tool serves a necessary function without redundancy, covering major tax obligations for Canadian self-employed individuals.

Completeness4/5

The toolset covers core self-employed tax math: CPP, overall tax estimate, deadlines, GST registration and method comparison, and instalments. Minor gaps exist (e.g., detailed deduction calculators, T2125 support), but agents can work with the provided set.

Resources