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

irs-taxpayer-mcp

by dma9527
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

plan_multi_year_taxes

Read-onlyIdempotent

Project federal taxes over 3–5 years to model income changes, Roth conversions, retirement contributions, and bracket management for strategic tax planning.

Instructions

Create a 3-5 year tax projection and strategy. Models income changes, Roth conversions, retirement contributions, and bracket management across multiple years.

Input Schema

NameRequiredDescriptionDefault
yearsYesYear-by-year projections
currentAgeYes
filingStatusYes

Output Schema

NameRequiredDescriptionDefault
textYes
errorNo
isErrorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.2.4
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / currentAge / maximum
      Added value: +9007199254740991
    • removedInput schema / properties / years / items / additionalProperties
      Removed value: -false
    • addedInput schema / properties / years / items / properties / dependents / maximum
      Added value: +9007199254740991
  2. Changed2 schema fields changedv1.0.1
    • changedInput schema / properties / years / items / properties / year / description
      Previous value: -"Tax year (2024 or 2025)"New value: +"Tax year (2024, 2025, or 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.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered, and 'projection' is consistent with a pure computation. The description adds useful context that this is a multi-year forward-looking model with specific levers, but omits that supported tax years appear limited to 2024-2026 in the schema while the text promises 3-5 years, a mismatch an agent should be warned about. No mention of assumptions, limits, or how projections are derived.

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?

Two sentences, purpose front-loaded before the supporting detail, with no filler. Minor redundancy between '3-5 year' and 'across multiple years' keeps it from a 5.

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?

An output schema exists, so return-value explanation is not required, and the purpose and levers are stated. The gap is the year-range claim: the description says 3-5 years while the schema allows 1-5 items with years restricted to 2024-2026, which could lead an agent to submit out-of-range planning horizons. For a planning tool of this complexity, that constraint belongs in the description.

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 only 33%, so the description must compensate and it partially does by naming expected income, Roth conversions, and IRA/401k contributions. However, three required parameters (filingStatus, currentAge, and the years array itself) plus stateCode and dependents get no added meaning. It also asserts a 3-5 year span while the schema permits 1-5 items, leaving the effective input range ambiguous.

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?

Specific verb and resource: 'Create a 3-5 year tax projection and strategy,' followed by the modeled levers (income changes, Roth conversions, retirement contributions, bracket management). It reads as a multi-year modeling tool, distinguishing it from single-year siblings like calculate_federal_tax or simulate_tax_scenario. It stops short of naming an alternative explicitly, so it does not reach 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?

Usage is only implied by the phrase 'multi-year' and by the listed modeling levers; there is no explicit statement of when to prefer this over compare_tax_years, generate_tax_plan, or simulate_tax_scenario. An agent can infer this is the many-year planning option, but must infer exclusions on its own.

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