Skip to main content
Glama
Sign In
irs-taxpayer-mcp

irs-taxpayer-mcp

by dma9527
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_tax_deadlines

Read-onlyIdempotent

Retrieve IRS tax deadlines and due dates for a specified tax year to plan filings and avoid missed deadlines.

Instructions

Get important IRS tax deadlines and due dates for a given tax year.

Input Schema

NameRequiredDescriptionDefault
taxYearNoTax year (default: 2026)

Output Schema

NameRequiredDescriptionDefault
textYes
errorNo
isErrorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.4
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed2 schema fields changedv1.0.1
    • changedInput schema / properties / taxYear / description
      Previous value: -"Tax year (default: 2025)"New value: +"Tax year (default: 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"
+}
  3. First observedv0.5.3

TDQS

B3.2/5.0
Behavior3/5

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

The description clarifies that the data is for a 'given tax year,' adding useful scoping context. However, the provided annotations already handle the safety profile (readOnlyHint: true), and the description does not disclose any additional behavioral complexities or data limitations beyond the scope.

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?

The definition is a single, concise sentence that puts the primary function first. It avoids jargon and unnecessary phrasing while remaining direct.

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?

For a simple lookup tool with minimal parameters, the description is sufficiently complete. The combination of the scope (deadlines), the resource (IRS), and the safety hints provided in annotations makes the definition a good starting point for an agent.

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?

Since the schema coverage is 100%, the baseline score is 3. The description merely confirms that the tool operates 'for a given tax year,' which is the exact role of the 'taxYear' parameter, thus adding no semantic value beyond the schema.

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 tool clearly states its purpose: retrieving IRS tax deadlines and due dates. While the purpose is clear, given the extremely long list of tax-related sibling tools, the description relies on the noun 'deadlines' to differentiate itself, which may not be fully sufficient.

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

Usage Guidelines2/5

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

The definition provides virtually no usage guidance. It does not explain when to use this tool versus closely related tools like 'get_tax_brackets' or 'get_personalized_tax_calendar,' making tool selection difficult for an agent without trial and error.

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

Deploy Server

Other Tools