irs-taxpayer-mcp

Overview Schema Source Related Servers Discussions Admin

get_tax_document_checklist

Read-onlyIdempotent

Generate a personalized checklist of tax documents by answering questions about your income, deductions, and life events. Get the exact documents you need to file your taxes.

Instructions

Generate a personalized checklist of tax documents you need to gather for filing. Based on your income sources, deductions, and life events.

Input Schema

TableJSON Schema

Name	Required	Description
`hasW2`	No	Have W-2 employment
`hasHSA`	No	Have HSA account
`hadBaby`	No	Had a baby this year
`boughtEV`	No	Bought an electric vehicle
`soldHome`	No	Sold a home this year
`gotMarried`	No	Got married this year
`gotDivorced`	No	Got divorced this year
`hasChildren`	No	Have dependent children
`hasMortgage`	No	Have a mortgage
`hasChildcare`	No	Pay for childcare
`hasInvestments`	No	Have investment accounts (stocks, bonds, crypto)
`installedSolar`	No	Installed solar panels
`hasStudentLoans`	No	Paying student loans
`hasRentalProperty`	No	Own rental property
`hasSelfEmployment`	No	Have self-employment/freelance income
`hasForeignAccounts`	No	Have foreign bank accounts or income
`hasHealthInsurance`	No	Have health insurance (marketplace or employer)
`hasEducationExpenses`	No	Paying tuition or student expenses
`hasCharitableDonations`	No	Made charitable donations
`hasRetirementContributions`	No	Contributed to IRA/401k

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

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds useful behavioral context by indicating that the checklist is personalized and driven by the user's income sources, deductions, and life events. This goes beyond the annotations without contradicting them.

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 sentences with no filler. The primary action and output are front-loaded, and the input basis is stated immediately after. Every sentence earns its place.

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?

Given the rich input schema with 20 well-documented boolean parameters, an output schema, and annotations covering idempotence and safety, the description is complete enough for an agent to select and invoke the tool correctly. It explains what the tool produces and what factors influence the result; return-value details are covered by the output 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 boolean parameter already has a clear description. The tool description's reference to 'income sources, deductions, and life events' provides a light conceptual grouping, but it does not add meaningful parameter semantics beyond what the schema already supplies. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Generate') and resource ('personalized checklist of tax documents'), and clearly states the purpose: helping gather documents for filing. This is distinct from sibling tools like get_tax_deadlines or calculate_total_tax, so an agent can immediately tell what this tool is for.

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

Usage Guidelines4/5

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

The phrase 'for filing' plus 'based on your income sources, deductions, and life events' gives clear context for when to use this tool: when a user needs a document-gathering checklist customized to their situation. It does not explicitly name alternatives or exclusions, but the purpose is sufficiently distinct among the sibling tools.

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

Deploy Server