AuraCalcs

Estimate 2026 1099 and self-employment tax

calculate_1099_tax

Read-only

Estimate 2026 tax on 1099 / self-employment income: self-employment tax (Social Security and Medicare, with its full breakdown), federal income tax, optional flat state tax, the percent of each payment to set aside, and the quarterly payment. Same math as the auracalcs.com 1099 tax and self-employment tax calculators. Returns a link to the page, sources, the date checked, and a disclaimer. 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": {
      "grossIncome": "<grossIncome>"
    },
    "name": "calculate_1099_tax"
  }
}

Input Schema

Name	Required	Description
`w2Wages`	No	Other W-2 wages this year. They use up the Social Security wage base first. Defaults to 0.
`grossIncome`	Yes	Total 1099 / self-employment income for 2026, before expenses.
`filingStatus`	No	single or married (filing jointly). Defaults to single.
`stateTaxRate`	No	Flat state income tax rate in percent, applied to AGI. Use 0 for no-income-tax states. Defaults to 0, so state tax is left out unless given.
`businessExpenses`	No	Deductible business expenses for the year. Defaults to 0.
`applyQbiDeduction`	No	Apply the 20% qualified business income deduction. Defaults to true, like the website.
`healthInsurancePremiums`	No	Self-employed health insurance premiums. Defaults to 0.
`retirementContributions`	No	SEP IRA or solo 401(k) contributions. Defaults to 0.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations only declare the read-only, non-destructive, closed-world safety profile, and the description goes beyond that by disclosing the return payload (link, sources, date checked, disclaimer) and framing the output as an estimate rather than tax advice. It also anchors trust by citing 'Same math as the auracalcs.com ... calculators', which annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core computation is front-loaded in the first sentence and the return-value sentence follows, with no filler. The long parenthetical and the website-comparison clause are slightly bulky but each carries real information.

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?

With no output schema, the description carries the burden of describing returns and does so adequately (breakdown, set-aside percent, quarterly payment, link, sources, date, disclaimer). For an 8-parameter tool it is nearly complete; only the state-tax and QBI behaviors are left entirely to the schema.

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 each of the 8 parameters carries a substantive description including defaults and edge-case notes (e.g. W-2 wages consuming the Social Security wage base, state rate 0 for no-income-tax states). The description itself adds no per-parameter meaning, so the baseline 3 applies.

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?

States a specific verb and resource ('Estimate 2026 tax on 1099 / self-employment income') and enumerates the computed outputs, so the agent knows exactly what the tool produces. It does not name or contrast with the closest sibling, calculate_quarterly_estimated_tax, even though it also returns a quarterly payment figure.

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 output enumeration (self-employment tax breakdown, set-aside percent, quarterly payment) plus the closing 'Estimate only.' There is no explicit when-to-use or when-not-to-use guidance and no routing to calculate_quarterly_estimated_tax or compare_1099_vs_w2, which an agent could easily confuse with this one.

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?