AuraCalcs

Plan 2026 quarterly estimated tax

calculate_quarterly_estimated_tax

Read-only

Work out 2026 federal quarterly estimated tax payments with the IRS safe harbor rules (90% of this year's tax or 100%/110% of last year's), minus withholding, with the four due dates. Same math as the auracalcs.com quarterly estimated tax calculator. Estimate only.

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": {
      "expectedTax2026": "<expectedTax2026>",
      "priorYearTax2025": "<priorYearTax2025>"
    },
    "name": "calculate_quarterly_estimated_tax"
  }
}

Input Schema

Name	Required	Description
`withholding`	No	Federal tax withheld from W-2 jobs in 2026. Defaults to 0.
`paymentsMade`	No	Estimated payments already made for 2026. Defaults to 0.
`expectedTax2026`	Yes	Expected total 2026 tax: federal income tax plus self-employment tax. calculate_1099_tax can estimate it.
`priorYearTax2025`	Yes	Total tax on the 2025 return (Form 1040 line 24). Use 0 only if 2025 had no tax liability and was a full 12-month year.
`priorYearAgiOver150k`	No	Was 2025 AGI over $150,000 ($75,000 if married filing separately)? Then the prior-year safe harbor is 110%. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish that this is a safe, read-only, non-destructive calculation. The description adds meaningful behavioral context by naming the safe-harbor formulas, subtracting withholding, and stating that it is an estimate only, though it does not describe the return format.

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 compact and front-loaded: it leads with the calculation and then adds the safe-harbor context and estimate-only caveat. Every sentence contributes useful information without excess.

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 five-parameter calculator with full schema descriptions and read-only annotations, the description gives enough context to understand the calculation and its limits. It could be slightly more complete by clarifying the returned quarterly amounts, but the due-date mention covers most of that gap.

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 the parameters are already well documented. The description adds some formula-level meaning around safe harbor and withholding, but it does not explain the roles of all five parameters, so the baseline of 3 is appropriate.

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?

The description states a specific verb and resource: working out 2026 federal quarterly estimated tax payments, including the safe-harbor rules and four due dates. The purpose is clear and distinct from the sibling calculators, though it does not explicitly differentiate itself from them.

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?

Usage is implied by the quarterly estimated tax framing and the 'Estimate only' caveat, but the description does not say when to choose this tool over siblings or when not to use it. No alternatives or exclusions are named.

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

All AuraCalcs tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?