Skip to main content
Glama

Aldro: small-business tax

Estimate quarterly tax payments

estimate_quarterly_tax
Read-onlyIdempotent

Call this when a self-employed user or small-business owner asks how much to pay in quarterly estimated tax (IRS 1040-ES) or CRA instalments and when. Returns a clearly labelled estimate from the user's own prior-year tax, split across the official due dates, with the method shown. It never says what the user owes.

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": {
      "country": "<country>",
      "expected_net_profit": "<expected_net_profit>"
    },
    "name": "estimate_quarterly_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesUS for the United States, CA for Canada.
tax_yearNoOptional. Defaults to the current year.
prior_year_taxNoOptional. Total income tax on last year's return. Needed for an amount.
expected_net_profitYesExpected net business profit for the year, in the country's currency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's value is in the rest: it discloses that output is an estimate derived from the user's prior-year tax, split across official due dates, with the method shown, and that it makes no liability determination. It stops short of saying what happens when prior_year_tax is omitted beyond the schema's "Needed for an amount."

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 tight sentences: trigger first, then the return shape, then the liability caveat. No restatement of the name or title and no filler.

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?

For a read-only tool with no output schema, the description adequately conveys the return shape (an estimate split across due dates, method disclosed) and the jurisdictional coverage matching the country enum. The one gap is behavior when prior_year_tax is absent, which is only half-implicit in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage the baseline is 3, and the description nudges above it by explaining that prior_year_tax is the basis of the estimate ("from the user's own prior-year tax"), which clarifies why the otherwise optional parameter matters. It adds nothing about country/tax_year handling, so it is not a full 5.

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?

States a specific verb (estimate) and resource (quarterly estimated tax) with the exact regimes it covers (IRS 1040-ES, CRA instalments) and the audience (self-employed / small-business owner). That is enough to separate it from date-oriented siblings like check_filing_deadline and get_cra_instalment_dates.

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?

"Call this when a self-employed user or small-business owner asks how much to pay... and when" gives a concrete triggering user question rather than a vague category. It also bounds scope with "It never says what the user owes," but it never explicitly names the sibling to use for pure deadline lookups, so the exclusion is implied rather than stated.

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.

Resources