Skip to main content
Glama
mcpwright
by mcpwright

Get state totals

get_state_totals
Read-only

Get a state's total returns, individuals, AGI, average AGI, income tax, total tax liability, and AGI distribution across six income brackets.

Instructions

State-level SOI totals and AGI distribution from the IRS state rollup.

`state`: a 2-letter USPS code (e.g. 'CA') or full state name (e.g.
'California'). Returns the state's total returns, individuals, AGI, average
AGI per return, income tax, total tax liability, and the income distribution
across the six AGI brackets. Drawn from the IRS 00000 state-total row.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateYes2-letter USPS state code
returnsNoTotal returns in the state
bracketsYesThe state's income distribution across the six AGI brackets
tax_yearYesSOI tax year of the data
income_taxNoTotal income tax amount
individualsNoTotal individuals (filers plus dependents)
avg_agi_per_returnNoAGI divided by the number of returns
total_tax_liabilityNoTotal tax liability amount
adjusted_gross_incomeNoTotal adjusted gross income (AGI)
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is established. The description adds transparency by specifying the data source ('IRS 00000 state-total row') and listing the exact fields returned, which enriches the behavioral context beyond the annotations.

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 efficiently structured: the first sentence states the purpose, the second details the parameter, and the third lists the returned fields. Every sentence contributes useful information without unnecessary verbosity.

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

Completeness4/5

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

With a single well-documented parameter and an output schema present, the description is nearly complete for a simple retrieval tool. It covers source, returned fields, and parameter format, leaving only minor gaps like error handling, but these are not critical given the output schema and annotation context.

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 input schema only defines the 'state' parameter with no description (0% schema coverage). The description fully compensates by explaining accepted formats (2-letter USPS code or full state name) with examples, providing essential semantic value.

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 purpose: to retrieve state-level SOI totals and AGI distribution from the IRS state rollup. It names the specific resource and differentiates from siblings by focusing on state-level aggregates rather than zip-level or single-metric tools.

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?

The description implies the tool is for state-level aggregate data but does not explicitly state when to use it over alternatives. No exclusions or alternative tool names are mentioned, so usage guidance is implied rather than explicit.

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