Skip to main content
Glama
dma9527

irs-taxpayer-mcp

by dma9527
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

calculate_eitc

Read-onlyIdempotent

Calculate the exact Earned Income Tax Credit amount based on your tax year, filing status, income, and qualifying children. Get a precise refundable credit estimate to plan your taxes.

Instructions

Calculate the exact Earned Income Tax Credit (EITC) amount. The EITC is one of the largest refundable credits for low-to-moderate income workers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agiYesAdjusted Gross Income
taxYearYesTax year (2024, 2025, or 2026)
earnedIncomeYesEarned income (wages, salary, self-employment)
filingStatusYes
investmentIncomeNoInvestment income (interest, dividends, capital gains)
qualifyingChildrenYesNumber of qualifying children (0-3)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
errorNo
isErrorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. First observedv0.5.3

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already disclose that the operation is read-only and idempotent, so the description does not need to restate that. It adds useful context that EITC is a refundable credit for low-to-moderate income workers, but it does not disclose operational behaviors such as phase-out limitations, tax-year-specific rules, or how special cases like married_filing_separately are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no fluff. The first sentence leads with the action, and the second adds brief helpful context about the credit. It is front-loaded, appropriately sized, and every sentence earns its place.

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?

Given an output schema, read-only annotations, and a schema covering most parameters, the description is nearly complete for selecting and invoking the tool. It could go further by noting a key eligibility rule such as the married_filing_separately exclusion or the investment income cap, but these are likely handled inside the calculation and are not necessary for basic invocation.

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 high at 83%, so the schema already documents most parameters. The description adds no parameter-level details beyond general EITC background; specifically, it does not clarify filingStatus semantics or investmentIncome restrictions, though the schema already names these fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: 'Calculate the exact Earned Income Tax Credit (EITC) amount.' This clearly states what the tool computes and distinguishes it from sibling tools like list_tax_credits or check_credit_eligibility, which have different purposes.

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 when to use the tool—whenever an exact EITC amount needs to be calculated—but it does not explicitly discuss alternatives or when not to use it. The tool's focused verb and resource make the main use case obvious, but no exclusions or sibling comparisons are provided.

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