irs-taxpayer-mcp

Overview Schema Source Related Servers Discussions Admin

generate_tax_plan

Read-onlyIdempotent

Create a deterministic, local, privacy-first tax plan with structured assumptions, calculation trace, source provenance, and explicit unsupported boundaries.

Instructions

Generate a deterministic, privacy-first local tax plan with structured results, assumptions, source provenance, calculation trace, and explicit unsupported boundaries.

Input Schema

Name	Required	Description
`family`	No
`income`	Yes	Annual income facts. Qualified dividends are included in ordinary dividends.
`taxYear`	Yes	Tax year: 2024, 2025, or 2026
`business`	No
`payments`	No
`education`	No
`stateCode`	No
`deductions`	No
`filingStatus`	Yes

Output Schema

Name	Required	Description	Default
`plan`	No
`text`	Yes
`error`	No
`isError`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed24 schema fields changedv1.2.4Nov 4, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / business / properties / materialParticipation

Added value: +{
+  "description": "TY2026+: materially participates, enabling the $400 minimum QBI deduction",
+  "type": "boolean"
+}

changedInput schema / properties / deductions / properties / itemized / description

Previous value: -"Eligible itemized deduction total after applicable limits"New value: +"Schedule A total after the SALT cap and medical floor, before the TY2026 charitable floor and IRC 68 limit"

addedInput schema / properties / deductions / properties / itemizedCharitable

Added value: +{
+  "description": "TY2026+: charitable portion of itemized, for the 0.5% of AGI floor",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / deductions / properties / itemizedStateAndLocalTaxes

Added value: +{
+  "description": "State and local taxes included in itemized after the SALT cap; added back for AMT (Form 6251 line 2a)",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / deductions / properties / nonItemizerCashCharitable

Added value: +{
+  "description": "TY2026+: qualifying cash gifts to public charities for the non-itemizer deduction",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / deductions / properties / qualifiedOvertimeCompensation

Added value: +{
+  "description": "TY2025+ Schedule 1-A FLSA overtime premium",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / deductions / properties / qualifiedTips

Added value: +{
+  "description": "TY2025+ Schedule 1-A qualified tips",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / deductions / properties / qualifiedVehicleLoanInterest

Added value: +{
+  "description": "TY2025+ Schedule 1-A interest on a new US-assembled personal vehicle loan",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / family / properties / age65OrOlder
```
Added value: +{
+  "type": "boolean"
+}
```
addedInput schema / properties / family / properties / dependentCareBenefitsExcluded
```
Added value: +{
+  "minimum": 0,
+  "type": "number"
+}
```
addedInput schema / properties / family / properties / dependentCareExpenses
```
Added value: +{
+  "minimum": 0,
+  "type": "number"
+}
```

addedInput schema / properties / family / properties / dependentCareQualifyingIndividuals

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / family / properties / otherDependentsForOdc / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / family / properties / qualifyingChildrenForCtc / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / family / properties / qualifyingChildrenForEitc / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / family / properties / spouseAge65OrOlder
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / family / properties / spouseEarnedIncome

Added value: +{
+  "description": "MFJ only: spouse's earned income, already included in household income",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / taxYear / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / taxYear / minimum
```
Added value: +-9007199254740991
```
addedOutput schema / properties / plan / properties / results / properties / dependentCareCredit
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / plan / properties / results / properties / itemizedDeductionLimitReduction
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / plan / properties / results / properties / nonItemizerCharitableDeduction
```
Added value: +{
+  "type": "number"
+}
```

changedOutput schema / properties / plan / properties / results / required

Previous value: -[
-  "adjustedGrossIncome",
-  "deductionType",
-  "deductionAmount",
-  "taxableIncome",
-  "ordinaryIncomeTax",
-  "capitalGainsTax",
-  "selfEmploymentTax",
-  "niit",
-  "additionalMedicareTax",
-  "amt",
-  "refundableCredits",
-  "federalTaxAfterRefundableCredits",
-  "employeeFica",
-  "stateTax",
-  "totalTax",
-  "takeHomeIncome",
-  "federalBalance",
-  "stateBalance",
-  "estimatedQuarterlyPayment",
-  "marginalRate",
-  "effectiveFederalRate"
-]New value: +[
+  "adjustedGrossIncome",
+  "deductionType",
+  "deductionAmount",
+  "nonItemizerCharitableDeduction",
+  "itemizedDeductionLimitReduction",
+  "taxableIncome",
+  "ordinaryIncomeTax",
+  "capitalGainsTax",
+  "selfEmploymentTax",
+  "niit",
+  "additionalMedicareTax",
+  "amt",
+  "dependentCareCredit",
+  "refundableCredits",
+  "federalTaxAfterRefundableCredits",
+  "employeeFica",
+  "stateTax",
+  "totalTax",
+  "takeHomeIncome",
+  "federalBalance",
+  "stateBalance",
+  "estimatedQuarterlyPayment",
+  "marginalRate",
+  "effectiveFederalRate"
+]

Changed3 schema fields changedv1.1.0Sep 23, 2026

addedInput schema / properties / stateCode / pattern
```
Added value: +"^[A-Za-z]{2}$"
```
addedOutput schema / properties / plan / properties / privacy / properties / modelInvoked
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / properties / plan / properties / privacy / required

Previous value: -[
-  "execution",
-  "networkRequests",
-  "persisted",
-  "telemetry"
-]New value: +[
+  "execution",
+  "networkRequests",
+  "persisted",
+  "telemetry",
+  "modelInvoked"
+]

Addedv1.0.1Sep 7, 2026

TDQS

B3.1/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, and non-destructive behavior. The description adds useful behavioral context: deterministic and privacy-first local computation, plus structured results, assumptions, source provenance, calculation trace, and explicit unsupported boundaries.

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?

It is a single front-loaded sentence with no wasted words. The list of output components is dense but informative, though it could be broken into a clearer structure.

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?

The output schema means return values need not be explained, and the description covers purpose and behavior. However, for a complex 9-parameter tool with nested objects and low schema coverage, the absence of input guidance and usage conditions leaves clear gaps.

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

Parameters1/5

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

Schema description coverage is only 22%, so the description should compensate for undocumented parameters. It mentions no parameter names, constraints, or input semantics whatsoever, leaving the agent reliant on the schema alone.

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: 'Generate a deterministic, privacy-first local tax plan' and lists the output components. It does not explicitly differentiate this from close siblings like generate_full_tax_report or calculate_total_tax, so sibling differentiation is missing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus alternatives. The many tax calculation and planning siblings make the absence of routing guidance significant.

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

Deploy Server