Skip to main content
Glama
mcpwright
by mcpwright

Compare ZIPs

compare_zips
Read-only

Rank multiple US ZIP codes by a chosen IRS statistic, from highest to lowest value. Missing or suppressed data is handled with clear indicators.

Instructions

Rank several ZIPs by a single metric, highest value first.

`zips`: a list of 5-digit US ZIPs to compare. `metric`: one of
`total_returns`, `adjusted_gross_income`, `avg_agi_per_return`,
`pct_returns_200k_plus`, `total_income`, `salaries_and_wages`, `income_tax`,
`total_tax_liability`, `avg_total_tax_per_return`, `eitc_amount`. Returns each
ZIP's value, sorted descending; ZIPs with no SOI data are listed last. A 0
for a sparse metric (e.g. `eitc_amount`) may be IRS-suppressed, not a true
zero.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zipsYes
metricYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metricYesThe compared metric's name
resultsYesOne entry per requested ZIP, sorted by value descending; ZIPs with no data are listed last
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 and openWorldHint, the description adds essential behavioral details: results sorted descending, ZIPs without SOI data listed last, and suppressed zeros potentially not representing true zeros. This significantly enhances transparency for the agent.

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 compact yet complete, front-loading the core action and then providing param semantics and behavior in a well-structured format. The metric list, while lengthy, is necessary and earns its place.

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 output schema exists, the description does not need to explain return values, but it still covers sorted order and missing-data handling. Both parameters are fully specified, making the tool's behavior complete for an agent.

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?

Despite zero schema description coverage, the description fully explains both parameters: `zips` as a list of 5-digit US ZIPs and `metric` with every possible enum value enumerated. This adds complete meaning beyond the bare 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 ranks several ZIPs by a single metric, specifically highest value first. It distinguishes itself from sibling tools by focusing on comparison across multiple ZIPs rather than single-lookup getters.

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 clearly conveys when to use this tool (comparing several ZIPs on one metric) and implies the scope of input. It does not explicitly state alternatives or when-not-to-use, but the context of siblings and the unique compare functionality provides clear usage context without exclusions.

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