irs-taxpayer-mcp

Overview Schema Source Related Servers Discussions Admin

get_tax_planning_tips

Read-onlyIdempotent

Generates personalized year-end tax planning tips based on income, filing status, deductions, and account details, then suggests actions to reduce tax liability before year-end.

Instructions

Get personalized year-end tax optimization strategies based on your income, deductions, and situation. Suggests actions to reduce tax liability before year-end.

Input Schema

Name	Required	Description
`hasHSA`	No	Have HSA-eligible health plan
`taxYear`	Yes	Tax year to plan for
`hasMortgage`	No
`filingStatus`	Yes
`isSelfEmployed`	No
`estimatedIncome`	Yes	Expected total income for the year
`hasCapitalGains`	No
`charitableGiving`	No	YTD charitable donations
`hasCapitalLosses`	No
`hasRetirementPlan`	No	Have access to 401k/403b
`currentWithholding`	No	Total tax already withheld/paid YTD
`estimatedCapitalGains`	No
`currentHSAContributions`	No	YTD HSA contributions
`estimatedItemizedDeductions`	No
`currentRetirementContributions`	No	YTD retirement contributions

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.2.4Nov 4, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```

Changed1 schema field changedv1.0.1Sep 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "error": {
+      "additionalProperties": false,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        },
+        "suggestion": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message",
+        "suggestion"
+      ],
+      "type": "object"
+    },
+    "isError": {
+      "type": "boolean"
+    },
+    "text": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "text",
+    "isError"
+  ],
+  "type": "object"
+}

First observedv0.5.3Feb 25, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed world, so safety is covered. The description usefully signals that this is advisory (it 'suggests actions') rather than a pure calculator, but adds nothing about the cost of a broad call, any limits, or whether results are deterministic across repeated calls with the same year.

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?

Two short sentences with the purpose front-loaded; no filler or marketing padding. The second sentence partly restates the first ('suggests actions to reduce tax liability' vs 'optimization strategies'), costing a little redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 15-parameter advisory tool the description is thin on parameter guidance, and an agent gets no signal that supplying more optional fields improves personalization, or how partial inputs are handled. With an output schema already documenting returns and annotations covering safety, this is a moderate gap rather than a blocking one.

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 coverage is 53%, and the description only loosely gestures at the parameter space with 'income, deductions, and situation'. It does not clarify that only taxYear, filingStatus and estimatedIncome are required, nor which optional booleans (hasHSA, isSelfEmployed, hasCapitalGains) materially change the advice.

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 ('Get personalized year-end tax optimization strategies') and scopes it to inputs the agent can recognize (income, deductions, situation). It does not, however, distinguish itself from close siblings such as generate_tax_plan or plan_multi_year_taxes, which an agent could easily confuse with this one.

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?

Timing is implied by 'year-end' and 'before year-end', which hints at the appropriate window, but there is no explicit when-to-use versus when-not, no mention of prerequisites, and no routing to the obvious alternatives (generate_tax_plan, plan_multi_year_taxes, optimize_capital_gains).

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

Deploy Server