foundation-discovery

Get IRS 990 Summary

get_990_summary

Read-only

Get IRS 990 filing summary and financial trends for a foundation.

This tool retrieves IRS 990 filing data (Form 990 or 990-PF) for a foundation, showing financial information over time. It calculates year-over-year trends for assets, grants, and revenue.

US 990 filers only. Pass ein (or a funder_id that resolves to an EIN — a bare EIN or usf:<ein>). search_funders returns funder_id on every hit, so the caller can hand it back here the way it does for the other funder tools. Non-990 funders have no 990 filings — those return a clean redirect to get_funder_stats(funder_id=...) rather than an error.

Input Schema

TableJSON Schema

Name	Required	Description
`ein`	No	Foundation EIN (9 digits). Can include hyphens (e.g., "94-3136777") or be provided as digits only (e.g., "943136777"). Optional if ``funder_id`` is supplied.
`years`	No	Number of years of filing data to return (1-10)
`funder_id`	No	Optional polymorphic funder id. A bare EIN or ``usf:<ein>`` routes to the 990 path; a non-990 id (bare UUID / ``n9f:<uuid>`` / ``non990:<uuid>``) has no 990 filings and returns a redirect to get_funder_stats.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 5, 2026

addedInput schema / properties / ein / default
```
Added value: +""
```

changedInput schema / properties / ein / description

Previous value: -"Foundation EIN (9 digits). Can include hyphens (e.g., \"94-3136777\")\n or be provided as digits only (e.g., \"943136777\")."New value: +"Foundation EIN (9 digits). Can include hyphens (e.g., \"94-3136777\")\n or be provided as digits only (e.g., \"943136777\"). Optional if\n ``funder_id`` is supplied."

addedInput schema / properties / funder_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional polymorphic funder id. A bare EIN or ``usf:<ein>``\n routes to the 990 path; a non-990 id (bare UUID / ``n9f:<uuid>`` /\n ``non990:<uuid>``) has no 990 filings and returns a redirect to\n get_funder_stats."
+}

removedInput schema / required
```
Removed value: -[
-  "ein"
-]
```

Changed2 schema fields changedJun 13, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / ein / description

Added value: +"Foundation EIN (9 digits). Can include hyphens (e.g., \"94-3136777\")\n or be provided as digits only (e.g., \"943136777\")."

Changed2 schema fields changedApr 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

removedInput schema / properties / ein / description

Removed value: -"Foundation EIN (9 digits). Can include hyphens (e.g., \"94-3136777\")\n or be provided as digits only (e.g., \"943136777\")."

First observedApr 28, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/destructive/openWorld. The description adds genuinely non-structured behavior: US-990-only scope, trend computation, and the fact that non-990 inputs produce a clean redirect rather than an error. Does not discuss pagination or result size limits, so not a full 5.

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?

Front-loaded with purpose and scope, then parameter routing and fallback behavior. Slightly verbose in restating the 990-vs-non-990 routing twice, but every sentence carries information.

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?

With an output schema present and annotations covering the safety profile, the description supplies everything else an agent needs: data scope, identity inputs, and the non-990 fallback path.

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

Parameters3/5

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

Schema description coverage is 100%, so ein/funder_id/years are already well documented. The description reiterates the ein vs funder_id relationship and the usf:<ein> form, which is largely redundant with the schema, though the search_funders handoff adds a small workflow hint.

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?

States a specific verb (get) and resource (IRS 990 filing summary / financial trends) and clearly distinguishes itself from get_funder_stats and get_funder_profile by declaring it is 990-only with a redirect for non-990 funders.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use (US 990 filers), how to supply identity (ein, or funder_id resolving to an EIN), and the alternative for non-990 funders (get_funder_stats). It even ties the workflow to search_funders returning funder_id.

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

All foundation-discovery tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?