Skip to main content
Glama
dma9527

irs-taxpayer-mcp

by dma9527
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_tax_brackets

Read-onlyIdempotent

Retrieve federal income tax brackets and standard deduction for a tax year and filing status. Find applicable tax rates for single, joint, separate, or head-of-household filers.

Instructions

Get federal income tax brackets and standard deduction for a given tax year and filing status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taxYearYesTax year (2024, 2025, or 2026)
filingStatusYesFiling status

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.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds that the tool returns both tax brackets and the standard deduction, which is useful scope information, but it does not discuss response size, pagination, or any other runtime behavior. No contradiction.

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?

A single 15-word sentence front-loads the verb and resource, then adds the two qualifiers. There is zero redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no explicit usage guidance, the definition is complete for a simple read-only lookup: annotations cover safety, schema covers all parameter constraints with 100% coverage, and an output schema exists to document the return shape. The description states the core resource and scope, so an agent can safely call it.

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%: taxYear is documented as 'Tax year (2024, 2025, or 2026)' and filingStatus has an explicit enum. The description only restates the two dimensions ('given tax year and filing status') without adding format constraints, allowed values, or edge-case handling, so it adds no meaning beyond the schema.

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 the specific verb 'Get' with a precise resource: 'federal income tax brackets and standard deduction,' qualified by 'tax year and filing status.' This clearly distinguishes it from state-tax siblings like get_state_tax_info and calculation tools like calculate_federal_tax.

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?

No explicit when-to-use or when-not-to-use statements; it does not name alternative tools or exclusion criteria. The description implies use when a specific federal tax year and filing status are known, but the agent must infer this from the purpose, and many siblings overlap thematically.

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