irs-taxpayer-mcp

Overview Schema Source Related Servers Discussions Admin

get_personalized_tax_calendar

Read-onlyIdempotent

Generate a tax calendar tailored to your filing situation. Provide tax year and details like self-employment, investments, or extension to see deadlines for filing, estimated payments, and key actions.

Instructions

Generate a personalized tax calendar based on your situation. Shows deadlines for filing, estimated payments, extensions, and key actions.

Input Schema

TableJSON Schema

Name	Required	Description
`taxYear`	Yes	Tax year to get calendar for
`hasEmployer`	No	Do you have W-2 employment?
`filedExtension`	No	Did you file an extension?
`hasInvestments`	No	Do you have investment accounts?
`isSelfEmployed`	No	Do you have self-employment income?
`hasRentalIncome`	No	Do you have rental property income?

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.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, and destructiveHint: false, fully covering the safety profile. The description adds contextual value by stating the output covers 'deadlines for filing, estimated payments, extensions, and key actions,' but it does not disclose any behavioral quirks beyond what annotations and the output schema already convey. No contradiction 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?

The description is two tight sentences with no wasted words. The action and resource are front-loaded in the first sentence, and the second sentence efficiently enumerates what the calendar includes.

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

Completeness4/5

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

With a rich output schema and annotations covering read-only and idempotent behavior, the description plus schema are largely sufficient for an agent to invoke the tool correctly. The only notable gap is the lack of guidance for choosing between this tool and get_tax_deadlines, but the optional parameters and required taxYear are documented in the 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%, so the parameters are fully documented in the input schema. The description's phrase 'based on your situation' reinforces the purpose of the boolean flags but adds no specific meaning beyond what the schema already provides for each parameter.

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 ('Generate') and a clear resource ('personalized tax calendar based on your situation'), and it enumerates the calendar's contents: 'deadlines for filing, estimated payments, extensions, and key actions.' However, it does not explicitly differentiate itself from the sibling tool get_tax_deadlines, which likely serves a similar purpose for non-personalized deadlines.

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?

Usage context is implied through the phrase 'based on your situation' and the word 'personalized,' which suggests this tool should be used when tailoring a calendar to individual circumstances. There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named, so the agent must infer selection criteria from the tool name and description alone.

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

Deploy Server