IRS 990 Nonprofit Data

search_nonprofits

Search for nonprofit organizations by name or keyword.

Searches the ProPublica Nonprofit Explorer database of IRS 990 filers.
Returns organization name, EIN, location, revenue, and tax status.

Args:
    query: Search keywords (e.g. 'food bank', 'habitat for humanity').
    state: Two-letter state abbreviation to filter by (e.g. 'CA', 'TX').
    ntee_code: NTEE major category code (1-10). 1=Arts, 2=Education,
        3=Environment, 4=Health, 5=Human Services, 6=International,
        7=Public Benefit, 8=Religion, 9=Mutual Benefit, 10=Unknown.
    c_code: IRS subsection code (e.g. 3 for 501(c)(3), 4 for 501(c)(4)).
    page: Zero-indexed page number (25 results per page).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No
`query`	Yes
`state`	No
`c_code`	No
`ntee_code`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It does not indicate that the tool is read-only, safe, or idempotent. There is no mention of rate limits, authentication, or error behavior. The description only states searching and returning fields, leaving safety unknown.

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 concisely written in about 150 words with a clear front-loaded purpose and a structured Args list. Every sentence adds value, though the Args format could be slightly more integrated.

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

Completeness3/5

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

The description covers parameters and general return fields but lacks details on pagination beyond the page parameter, error handling, or output schema structure. With an output schema available, return values are partially covered, but behavioral context is minimal.

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

Parameters4/5

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

Schema description coverage is 0%, but the tool description includes a detailed 'Args' section explaining all five parameters, including default values, format for state, and enumeration for ntee_code. This adds significant meaning beyond the bare schema definitions.

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 starts with 'Search for nonprofit organizations by name or keyword', clearly stating the verb and resource. It specifies the ProPublica Nonprofit Explorer database and lists returned fields. Sibling tools get_nonprofit_details and get_nonprofit_filings handle distinct tasks, so this tool's purpose is well-differentiated.

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 usage for finding nonprofits but does not explicitly state when to use this tool over the siblings. It lacks guidance on alternatives, scope, or prerequisites. The Args section provides parameter details but no situational advice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All IRS 990 Nonprofit Data tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: search_nonprofits for finding EINs by name/keyword, get_nonprofit_details for comprehensive data on a specific EIN, and get_nonprofit_filings for filing history. No overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case (search_nonprofits, get_nonprofit_details, get_nonprofit_filings). The verbs are clear actions and nouns specify the resource.

Tool Count4/5

With 3 tools, the set is small but appropriately scoped for querying IRS 990 data. It covers search, detailed lookups, and filing histories without unnecessary bloat.

Completeness4/5

The tool surface covers key operations: search, retrieve details, and get filing history. However, there is no tool to retrieve a specific filing document (e.g., raw PDF), which could be a minor gap for users needing full forms.

Resources

Need Help?