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

irs-taxpayer-mcp

by dma9527
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

estimate_state_tax

Read-onlyIdempotent

Calculate state income tax for a specified state and tax year using an explicit calculation profile; unsupported state-year combinations are rejected.

Instructions

Estimate state income tax using an explicit tax-year calculation profile. Unsupported state-year paths fail closed.

Input Schema

NameRequiredDescriptionDefault
taxYearYesTax year for the versioned state calculation profile
stateCodeYesTwo-letter state code
filingStatusNoFiling status (default: single)
taxableIncomeNoDeprecated alias for incomeBeforeStateDeductions
incomeBeforeStateDeductionsNoState income before the modeled state standard deduction and personal exemption

Output Schema

NameRequiredDescriptionDefault
textYes
errorNo
isErrorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.2.4
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / taxYear / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / taxYear / minimum
      Added value: +-9007199254740991
  2. Changed5 schema fields changedv1.0.1
    • addedInput schema / properties / incomeBeforeStateDeductions
      Added value: +{
+  "description": "State income before the modeled state standard deduction and personal exemption",
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / taxYear
      Added value: +{
+  "description": "Tax year for the versioned state calculation profile",
+  "type": "integer"
+}
    • changedInput schema / properties / taxableIncome / description
      Previous value: -"State taxable income (after state deductions)"New value: +"Deprecated alias for incomeBeforeStateDeductions"
    • changedInput schema / required
      Previous value: -[
-  "stateCode",
-  "taxableIncome"
-]New value: +[
+  "stateCode",
+  "taxYear"
+]
    • 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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds one genuinely new behavioral trait — that unsupported state-year combinations fail closed rather than approximating — which is useful. It does not say what such a failure looks like or what the output contains, but an output schema exists to cover that.

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 short sentences with the purpose front-loaded and no filler. The second sentence is compact but leans on terser jargon ("fail closed") that costs a moment of interpretation, keeping it just short of ideal.

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?

With annotations covering safety, a full-coverage schema, and an output schema, the description only needs to add routing and edge-case context. It supplies the fail-closed caveat but omits any differentiation from the numerous sibling tax-calculation tools, which is the main remaining gap for a 5-parameter estimator in a crowded toolset.

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 every parameter including the deprecated taxableIncome alias is documented in the schema itself. The description only echoes that the calculation is tied to a versioned tax-year profile and adds no format, default, or precedence guidance beyond the schema; baseline 3 applies.

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?

States a specific verb and resource ("Estimate state income tax") plus a scoping notion (versioned tax-year calculation profile), so the agent knows this is a state-level estimation keyed to a year. It does not explicitly distinguish itself from near-siblings such as compare_state_taxes, get_state_tax_info, or compare_tax_years, leaving that inference to the agent.

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?

"Unsupported state-year paths fail closed" hints at a precondition (only certain state-year profiles are modeled) but never states when to choose this over calculate_federal_tax, compare_state_taxes, or get_state_tax_info. There are no explicit when-to-use or when-not-to-use instructions, only an implied failure condition.

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