IRS 990 Nonprofit Data

get_nonprofit_details

Get detailed information about a nonprofit organization by EIN.

Returns comprehensive data from the organization's IRS 990 filings
including revenue, expenses, assets, executive compensation, and
filing history. Use search_nonprofits first to find the EIN.

Args:
    ein: Employer Identification Number (e.g. '13-1837418' or '131837418').

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ein`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.6/5.0

Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool returns data from IRS 990 filings, which implies a read-only operation with no destructive side effects. It does not mention authentication or rate limits, but for a data retrieval tool, the description adequately conveys behavior.

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 two efficient paragraphs. The first states purpose and lists contents; the second gives usage hint and parameter details. No unnecessary words, every sentence adds value.

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 single parameter, clear output description, and presence of an output schema, the description covers all necessary information. The list of returned data types (revenue, expenses, etc.) provides sufficient context for the 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?

Schema description coverage is 0%, but the description thoroughly explains the 'ein' parameter with format examples ('13-1837418' or '131837418'), adding value beyond the schema's empty description. This fully compensates for the lack of schema documentation.

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 retrieves detailed nonprofit info by EIN, listing specific data categories (revenue, expenses, etc.). It distinguishes from siblings by mentioning 'Use search_nonprofits first' and implying get_nonprofit_filings is for filings.

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?

It explicitly advises to use search_nonprofits first to find the EIN, providing a sequential workflow hint. It could be improved by explicitly stating when not to use this tool (e.g., for filing-specific queries use get_nonprofit_filings), but the current guidance is clear.

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?