Skip to main content
Glama
mcpwright
by mcpwright

Get a raw SOI field

get_soi_field
Read-only

Get any single IRS SOI statistic for a U.S. ZIP code: provide a field code (e.g., A00100 for AGI) to receive the summed value, label, and unit across income brackets.

Instructions

Raw value of a single SOI field for a ZIP — an escape hatch.

`zip_code`: a 5-digit US ZIP. `field`: a SOI field code (e.g. `A00100` for
AGI, `N1` for number of returns); case-insensitive. Returns that field summed
across the ZIP's AGI brackets, with its label and unit (USD for amount fields,
count for return counts). Limited to the fields held in the local store (the
same ones the other tools draw on); an unknown field errors with the list.

Note: a 0 may be IRS-suppressed (<20 returns in a cell) rather than a true
zero, and a sum over suppressed cells slightly understates the real total.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldYes
zip_codeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
unitYes'USD' for amount fields, 'count' for return counts
fieldYesSOI field code, e.g. 'A00100' or 'N1'
labelYesHuman-readable description of the field
stateNo2-letter USPS state code
valueNoThe field's value for this ZIP (summed over brackets)
zipcodeYes5-digit ZIP code
tax_yearYesSOI tax year of the data
Behavior5/5

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

Beyond the readOnlyHint=true annotation, the description discloses return semantics (summed across AGI brackets, includes label and unit), case-insensitivity, error behavior for unknown fields, and the IRS-suppression caveat. This is rich context that heavily informs the agent about outputs and edge cases, far exceeding the annotation baseline.

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

Conciseness4/5

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

The description is well-structured: a one-sentence purpose lead, followed by parameter details and a caution note. Every sentence carries necessary information, though slightly verbose with the inclusion of examples and caveats. It remains appropriately sized for the tool's complexity.

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 description covers the tool's scope, parameters, return value semantics, error behavior, and data caveats. Since an output schema exists, it doesn't need to detail the response shape further. For a 2-parameter read-only tool, this is fully complete.

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?

Schema coverage is 0%, so the description fully compensates by defining both parameters: zip_code as '5-digit US ZIP' and field as a 'SOI field code' with examples (A00100, N1) and case-insensitivity. This gives complete practical meaning to the schema's bare property names.

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's function: 'Raw value of a single SOI field for a ZIP — an escape hatch.' This specifies a distinct resource (single SOI field) and verb (get raw value), and differentiates it from siblings by emphasizing it's a raw/escape-hatch access to underlying data rather than a standardized aggregate tool.

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 description implies usage context via 'escape hatch' and notes the tool is 'Limited to the fields held in the local store (the same ones the other tools draw on).' This gives clear sense of when to use it (raw field access, when other tools don't expose it) but does not explicitly name alternatives or state when not to use it, leaving some implicit guidance.

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