Skip to main content
Glama
irs-taxpayer-mcp

irs-taxpayer-mcp

by dma9527

compare_tax_years

Read-onlyIdempotent

Calculate tax liability across different tax years for the same income, revealing how bracket changes and inflation adjustments alter the amount owed.

Instructions

Compare tax liability across different tax years for the same income. Shows how bracket changes and inflation adjustments affect your tax.

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": {
      "filingStatus": "<filingStatus>",
      "grossIncome": "<grossIncome>"
    },
    "name": "compare_tax_years"
  }
}

Input Schema

NameRequiredDescriptionDefault
dependentsNo
grossIncomeYesGross income to compare across years
filingStatusYes
selfEmploymentIncomeNo

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. Changed1 schema field changedv1.0.1
    • 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 this as a safe, read-only, idempotent, closed-world computation, so the safety profile is covered. The description usefully adds that the output explains bracket changes and inflation adjustments, which tells the agent what the comparison contains. However, it never says which tax years are compared or how they are chosen — a significant behavioral gap given no year parameter exists in the schema.

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, no filler, with the core purpose front-loaded in the first clause. The second sentence is informative rather than redundant. Slightly more length would be justified if it addressed the missing year-selection behavior.

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 values need not be explained, and the annotations cover the safety profile. The remaining gap is substantive: the description promises comparison 'across different tax years' while the input schema exposes no year parameters, so an agent cannot determine which years will be used or whether the set is fixed. That ambiguity should have been resolved in the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%: just grossIncome is documented, leaving filingStatus, dependents, and selfEmploymentIncome undocumented in the schema. The description contributes nothing about any parameter — it does not explain that selfEmploymentIncome is treated separately from grossIncome, how dependents affect the comparison, or that filingStatus drives the bracket lookup. With low coverage, this is the dimension where the description most needed to compensate and does not.

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 and resource ('Compare tax liability across different tax years') and adds a scoping condition ('for the same income'), which distinguishes it from broad multi-year planning siblings like plan_multi_year_taxes. It stops short of naming the closest alternatives (what_changed_between_tax_years, compare_filing_statuses), so it is clear but not fully differentiated.

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: 'for the same income' signals a controlled comparison, but there is no explicit when-to-use statement, no when-not, and no pointer to the sibling that handles year-over-year rule changes (what_changed_between_tax_years) or multi-year planning (plan_multi_year_taxes). An agent must infer the routing decision.

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