irs-taxpayer-mcp

Overview Schema Source Related Servers Discussions Admin

get_tax_planning_tips

Read-onlyIdempotent

Generate personalized year-end tax strategies from your income, deductions, and situation. Identify actions to reduce tax liability before the deadline.

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

TableJSON 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

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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

B3.2/5.0

Behavior3/5

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

Annotations (readOnlyHint=true, destructiveHint=false) already cover the safety profile, and the description aligns with those by using 'Get' and 'Suggests'. It adds some output context by saying the tool 'suggests actions,' but does not disclose whether the response is a ranked list, a single strategy, or if there are limitations like 'not financial advice.' With annotations covering the safety profile, a 3 is appropriate.

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 two short sentences with no redundancy. The primary purpose is front-loaded ('Get personalized year-end tax optimization strategies') and the second sentence adds clarifying output context without wasting words.

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

Completeness2/5

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

This tool has 15 parameters, 3 required, and an output schema, yet the description gives only a high-level overview. It does not mention required inputs (taxYear, filingStatus, estimatedIncome), how optional parameters factor in, or any scope limitations (e.g., US federal only). For a tool of this complexity, the description is too sparse to fully orient an agent.

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

Parameters2/5

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

Schema description coverage is only 53%, leaving several parameters (hasMortgage, isSelfEmployed, hasCapitalGains, hasCapitalLosses, estimatedCapitalGains, estimatedItemizedDeductions) undocumented. The description only broadly references 'income, deductions, and situation' and does not compensate for the missing parameter explanations. It also omits the required taxYear parameter entirely, leaving the agent to infer that it is needed.

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 clearly states a specific verb and resource: 'Get personalized year-end tax optimization strategies' and further clarifies it 'Suggests actions to reduce tax liability before year-end.' This distinguishes it from calculation and factual tools like calculate_total_tax or get_tax_brackets. However, it does not explicitly differentiate from the similarly broad sibling generate_tax_plan, so it falls short of a 5.

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?

The phrase 'year-end tax optimization strategies' implies when to use the tool (before year-end, for personalized tax-saving advice), but gives no explicit when-not-to-use guidance or alternative routing. An agent must infer usage from the year-end context, and there is no mention of when to choose generate_tax_plan or plan_multi_year_taxes instead.

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

Deploy Server