Skip to main content
Glama
mcpwright
by mcpwright

Get tax by ZIP

get_tax
Read-only

Retrieve IRS tax statistics for a U.S. ZIP code, including income tax, total tax liability, and average per return.

Instructions

Tax measures for a ZIP: income tax, total liability, and average per return.

`zip_code`: a 5-digit US ZIP. Returns income tax, income tax before credits,
total tax liability (broader — includes self-employment tax and other taxes),
total tax payments, and the average total tax per return. Amounts in USD.

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
income_taxNoIncome tax amount (after credits, before other taxes)
total_tax_paymentsNoTotal tax payments amount
total_tax_liabilityNoTotal tax liability (broader than income tax: includes self-employment tax, recapture, etc.)
avg_total_tax_per_returnNoTotal tax liability divided by the number of returns
income_tax_before_creditsNoIncome tax before credits amount
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, covering safety. The description adds valuable behavioral context: it explains what the broader total liability includes (self-employment tax, other taxes), specifies that amounts are in USD, and clarifies the ZIP format. This goes beyond the schema, though it could mention edge cases (e.g., invalid ZIPs), hence a 4.

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: first a high-level summary, then parameter detail and return list. Every sentence contributes information without fluff. It is front-loaded with the main purpose and structured logically.

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?

The tool has an output schema, but the description still explains the returned fields, which is helpful. All relevant context—purpose, parameter, return metrics, currency—is provided. The description is complete for a simple query tool, with no missing operational details expected for this complexity.

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

Parameters5/5

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

The schema only provides the parameter name 'Zip Code' with 0% description coverage. The tool description fully compensates by specifying the exact format ('5-digit US ZIP') and its purpose in the query. This adds meaning beyond the raw schema, making the parameter semantics clear.

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 clearly states the tool retrieves tax measures for a given ZIP code, enumerating specific metrics (income tax, total liability, average per return). It distinguishes from sibling tools like get_income or get_credits by focusing on aggregate tax measures and explicitly noting the broader total tax liability including self-employment tax.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The context is clear: use this tool when you need tax data for a 5-digit US ZIP code, with a list of returned metrics. It implies when to use this over more specific tools like get_income (which likely focuses on income tax only), but does not explicitly name alternatives or exclusions, so it stops short of a 5.

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