Skip to main content
Glama
mcpwright
by mcpwright

Get filing status by ZIP

get_filing_status
Read-only

Retrieve filing status breakdown for any U.S. ZIP code: counts of single, married-joint, head-of-household returns, plus elderly filers and e-file share.

Instructions

Filing-status mix for a ZIP: single / married-joint / head-of-household.

`zip_code`: a 5-digit US ZIP. Returns the number of single, married-filing-
jointly, and head-of-household returns, the number of elderly returns (age
65+), and the count and share of electronically filed returns.

Note: a 0 count may be IRS-suppressed (<20 returns in each AGI-bracket
cell) rather than truly absent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zip_codeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateNo2-letter USPS state code
zipcodeYes5-digit ZIP code
tax_yearYesSOI tax year of the data
total_returnsNoTotal number of returns
single_returnsNoSingle returns
elderly_returnsNoReturns with the taxpayer aged 65 or older
married_joint_returnsNoMarried-filing-jointly returns
electronically_filed_pctNoPercent of returns filed electronically (0-100)
head_of_household_returnsNoHead-of-household returns
electronically_filed_returnsNoElectronically filed returns
Behavior4/5

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

Beyond readOnlyHint, the description discloses IRS suppression behavior for 0 counts, a critical nuance not captured in annotations. It also defines 'elderly returns' as age 65+, adding valuable specificity.

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 efficient, covering purpose, parameters, and a caveat in three concise sentences with no redundancy.

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?

For a low-complexity tool with an existing output schema, the description completely covers the input format, return metrics, and an important data-quality note. No critical information is missing.

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 type/name, but the description explains that zip_code must be a 5-digit US ZIP. This is essential for correct invocation and adds 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 clearly states the tool returns filing-status mix (single, married-joint, head-of-household) for a ZIP, using the specific verb 'get'. It distinguishes from siblings like get_income or get_agi_distribution by focusing on filing status.

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 ZIP-specific scope is obvious from the description, making the intended use clear. However, it does not explicitly mention when not to use this tool or reference alternatives, so it falls 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