irs-taxpayer-mcp

Overview Schema Source Related Servers Discussions Admin

run_tax_health_check

Read-onlyIdempotent

Analyze your financial picture with a tax health check to surface missed credits, withholding errors, deduction gaps, audit risks, retirement shortfalls, and year-end planning tips.

Instructions

One-click tax health check. Analyzes your full financial picture and outputs a report with actionable findings: missed credits, withholding accuracy, deduction optimization, audit risk, retirement savings gaps, and year-end planning tips.

Input Schema

TableJSON Schema

Name	Required	Description
`age`	No
`taxYear`	Yes	Tax year
`boughtEV`	No
`w2Income`	No
`isStudent`	No
`stateCode`	No
`dependents`	No
`grossIncome`	Yes
`capitalGains`	No
`filingStatus`	Yes
`retirementIRA`	No
`installedSolar`	No
`retirement401k`	No
`federalWithheld`	No
`stateLocalTaxes`	No
`hsaContributions`	No
`mortgageInterest`	No
`hasHealthInsurance`	No
`charitableDonations`	No
`selfEmploymentIncome`	No

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

A3.5/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful context by stating that it outputs a report with specific actionable findings, which clarifies it is an analysis/diagnostic tool rather than a filing or calculation tool. No contradiction with annotations exists.

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?

Two tight sentences: the first states the high-level purpose, and the second enumerates the report's value areas. There is no filler, and the structure is front-loaded and scannable.

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 description covers the tool's purpose and report contents, and the output schema likely documents return structure. However, given the high complexity (20 parameters) and overlapping sibling tools, the description lacks guidance on when to choose this over similar broad tools and what inputs are expected.

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 5%, and the description does not compensate for this. It vaguely references the 'full financial picture' but never explains how the 20 parameters map to the report, which parameters matter most, or what values are expected. The required fields are left entirely implicit.

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 identifies a specific resource and action: analyzing the user's full financial picture and producing a health-check report. The list of finding categories makes the scope concrete, though it does not explicitly differentiate itself from overlapping siblings like generate_full_tax_report or assess_audit_risk.

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 'One-click tax health check' and 'full financial picture' imply a broad, comprehensive assessment, which suggests use for an overall review rather than a narrow calculation. However, the description provides no explicit when-to-use guidance or exclusions naming alternative tools.

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

Deploy Server