Skip to main content
Glama
irs-taxpayer-mcp

irs-taxpayer-mcp

by dma9527

calculate_w4_withholding

Read-onlyIdempotent

Calculate recommended W-4 withholding settings and estimate per-paycheck federal tax, with step-by-step form recommendations based on salary, filing status, dependents, and pay frequency.

Instructions

Calculate recommended W-4 withholding settings. Estimates per-paycheck federal tax and provides step-by-step W-4 form recommendations.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "taxYear": "<taxYear>",
      "filingStatus": "<filingStatus>",
      "annualSalary": "<annualSalary>",
      "payFrequency": "<payFrequency>"
    },
    "name": "calculate_w4_withholding"
  }
}

Input Schema

NameRequiredDescriptionDefault
taxYearYesTax year (2024, 2025, or 2026)
deductionsNoExpected itemized deductions (if more than standard)
dependentsNoNumber of qualifying child dependents
otherIncomeNoOther annual income (interest, dividends, side gigs)
spouseWorksNoDoes your spouse also work?
annualSalaryYesAnnual salary from this job
filingStatusYesFiling status
multipleJobsNoDo you hold multiple jobs simultaneously?
payFrequencyYesHow often you get paid

Output Schema

NameRequiredDescriptionDefault
textYes
errorNo
isErrorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.4
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / dependents / maximum
      Added value: +9007199254740991
  2. Changed2 schema fields changedv1.0.1
    • changedInput schema / properties / taxYear / 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?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds that output is a recommendation with step-by-step form guidance and per-paycheck estimates, which is useful context, but it says nothing about accuracy caveats, assumptions, or what the recommendation is based on.

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, front-loaded with the core action, with no filler. Slightly redundant between 'W-4 withholding settings' and 'W-4 form recommendations' but nothing wasteful.

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 a full output schema and complete parameter documentation, the description covers the basic contract. However, for a tool with nine inputs including multipleJobs and spouseWorks, it omits guidance on which inputs matter and why, and doesn't indicate limitations versus analyze_paycheck or calculate_federal_tax.

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% across all nine parameters, so the schema already documents taxYear, filingStatus, dependents, and the rest. The description contributes no additional parameter meaning, which is the expected baseline when the schema does the heavy lifting.

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: calculates recommended W-4 withholding settings and estimates per-paycheck federal tax. This implicitly distinguishes it from calculate_federal_tax and analyze_paycheck by its W-4/form-recommendation focus, but it never names a sibling, so differentiation is left to inference.

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?

The description implies the use case (setting up or adjusting W-4 withholding) but gives no explicit when-to-use or when-not guidance and never points to alternatives such as calculate_federal_tax, analyze_paycheck, or simulate_tax_scenario.

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