Skip to main content
Glama
mcpwright
by mcpwright

Get deductions by ZIP

get_deductions
Read-only

Retrieve standard and itemized deduction amounts, SALT deduction, and itemization rates for any U.S. ZIP code using IRS data.

Instructions

Deduction measures for a ZIP: standard vs. itemized, plus SALT.

`zip_code`: a 5-digit US ZIP. Returns the count and amount of standard
deductions and itemized deductions, the taxes-paid (SALT) deduction, and the
percent of returns that itemized. Amounts in USD.

Note: a 0 may be IRS-suppressed (<20 returns in each AGI-bracket cell)
rather than a true zero — it does not prove no one in the ZIP itemizes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zip_codeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateNo2-letter USPS state code
returnsNoNumber of returns
zipcodeYes5-digit ZIP code
tax_yearYesSOI tax year of the data
salt_amountNoTaxes-paid (SALT) deduction amount
salt_returnsNoNumber of returns with the taxes-paid (SALT) deduction
itemizing_pctNoPercent of returns that itemized rather than took the standard deduction (0-100)
itemized_amountNoTotal itemized deductions amount
itemized_returnsNoNumber of returns with itemized deductions
standard_deduction_amountNoStandard deduction amount
standard_deduction_returnsNoNumber of returns claiming the standard deduction
Behavior4/5

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

The description adds important behavioral context beyond the annotations: it explains that a 0 may be IRS-suppressed rather than a true zero, which is a critical interpretation caveat. It also states the return includes counts, amounts, and percentages. Since annotations already convey read-only and open-world semantics, this additional note about data suppression provides meaningful insight, though it does not cover all possible edge cases.

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 concise and front-loaded, starting with a clear purpose statement, then a focused parameter explanation, then return details, and finally a brief caveat. Every sentence earns its place with no unnecessary filler. It is well-structured and easy to scan.

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?

Given the presence of an output schema, the description does not need to enumerate every return field, but it still summarizes the key outputs (counts, amounts, SALT, percent itemized). It explains the zip_code parameter and provides the crucial IRS-suppression caveat. With the annotations indicating read-only and open-world behavior, this description is complete for making a correct tool invocation.

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

Parameters4/5

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

The input schema only defines zip_code as a string with no description (0% schema coverage). The description compensates by specifying 'a 5-digit US ZIP' and explaining what the parameter is used for (returns deduction measures for that ZIP). This adds the necessary format and semantic meaning beyond the schema, but could go further with examples or valid values.

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 opens with 'Deduction measures for a ZIP: standard vs. itemized, plus SALT,' which clearly identifies the resource (deductions) and scope (ZIP). The tool name 'get_deductions' supplies the verb, and the distinction from sibling tools like get_income or get_tax is implicit. However, the description lacks an explicit verb phrase, so it falls just short of a 5.

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?

The description provides no guidance on when to use this tool versus the sibling tools. It does not mention alternative tools like get_tax or compare_zips, nor does it state any exclusions or prerequisites. The only implied context is that it is for ZIP-level deduction measures, but the description does not explicitly help the agent decide between this and related tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mcpwright/soi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server