FundingLandscape

Get Foundation Details

get_foundation

Read-onlyIdempotent

Get the current profile for a PRIVATE foundation by EIN. Foundation Intelligence Beta uses active QA-gated releases for filing-scoped public facts and Plus grant-history and repeat-grantee sections. The Pro leadership section returns only people and titles exactly as listed in a dated public filing, with responsible-use limits. The Pro federal-connections section returns registry-corroborated organization-level overlap with federal assistance records. Named-person grant recipients and grant-purpose text are excluded. Only private foundations (IRS 990-PF filers, 3,678+ foundations) are included. Covers IRS tax years 2018 to 2026. Does not count toward your monthly searches.

Input Schema

TableJSON Schema

Name	Required	Description
`ein`	Yes	9-digit EIN (no dashes). Example: 911663695. Must be a private foundation (990-PF filer).
`page`	No	For federal_connections, 1-based results page.
`year`	No	For grant_history, filter by filing year.
`limit`	No	Rows per paid page (default 25, max 100). Federal connections uses page-number pagination; grant history and repeat grantees return opaque cursors.
`state`	No	For grant_history or federal_connections, filter by 2-letter recipient state.
`cursor`	No	Opaque cursor returned by the prior page.
`section`	No	Foundation Intelligence section. Grant history and repeat grantees require Plus; filing-listed leadership and federal-recipient connections require Pro.
`recipient`	No	Filter grant-history or repeat-grantee rows by organization name.
`minimum_years`	No	For repeat_grantees, minimum covered filing years (2+).
`maximum_amount`	No	For grant_history, maximum amount per reported line.
`minimum_amount`	No	For grant_history, minimum amount per reported line.
`assistance_listing_number`	No	For federal_connections, filter by Assistance Listing number such as 93.855.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedAug 31, 2026

addedInput schema / properties / assistance_listing_number

Added value: +{
+  "description": "For federal_connections, filter by Assistance Listing number such as 93.855.",
+  "type": "string"
+}

addedInput schema / properties / cursor

Added value: +{
+  "description": "Opaque cursor returned by the prior page.",
+  "type": "string"
+}

removedInput schema / properties / include_grants

Removed value: -{
-  "description": "Include recent grants (up to 20). Default: true",
-  "type": "boolean"
-}

addedInput schema / properties / limit

Added value: +{
+  "description": "Rows per paid page (default 25, max 100). Federal connections uses page-number pagination; grant history and repeat grantees return opaque cursors.",
+  "type": "number"
+}

addedInput schema / properties / maximum_amount

Added value: +{
+  "description": "For grant_history, maximum amount per reported line.",
+  "type": "number"
+}

addedInput schema / properties / minimum_amount

Added value: +{
+  "description": "For grant_history, minimum amount per reported line.",
+  "type": "number"
+}

addedInput schema / properties / minimum_years

Added value: +{
+  "description": "For repeat_grantees, minimum covered filing years (2+).",
+  "type": "number"
+}

addedInput schema / properties / page

Added value: +{
+  "description": "For federal_connections, 1-based results page.",
+  "type": "number"
+}

addedInput schema / properties / recipient

Added value: +{
+  "description": "Filter grant-history or repeat-grantee rows by organization name.",
+  "type": "string"
+}

addedInput schema / properties / section

Added value: +{
+  "description": "Foundation Intelligence section. Grant history and repeat grantees require Plus; filing-listed leadership and federal-recipient connections require Pro.",
+  "enum": [
+    "public_profile",
+    "grant_history",
+    "repeat_grantees",
+    "leadership",
+    "federal_connections"
+  ],
+  "type": "string"
+}

addedInput schema / properties / state

Added value: +{
+  "description": "For grant_history or federal_connections, filter by 2-letter recipient state.",
+  "type": "string"
+}

addedInput schema / properties / year

Added value: +{
+  "description": "For grant_history, filter by filing year.",
+  "type": "number"
+}

First observedJun 13, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, establishing a safe read operation. The description adds substantial behavioral detail beyond this: data freshness (QA-gated releases), section-specific behavior (leadership returns exact filing text with responsible-use limits, federal connections are registry-corroborated), exclusions (named-person recipients and grant-purpose text), coverage (2018–2026), and the operational note about not counting toward monthly searches. This fully transparent disclosure exceeds the annotation baseline.

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 longer than ideal but is front-loaded with the core purpose, then systematically covers sections, tiers, exclusions, coverage, and usage notes. Each sentence conveys a distinct piece of information with no filler or tautology. The structure flows logically from what the tool does, to what it returns per section, to limitations, making it reasonably scannable despite its length.

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 tool's complexity—12 parameters, 5 sections, tier-based access, multiple pagination schemes, and no output schema—the description covers all essential aspects an agent needs: what data is available per section, which tier is required, what is excluded, the tax-year coverage, and the usage quota. It even clarifies pagination differences (page numbers vs. cursors) and provides the required EIN format. Nothing critical is missing for correct invocation.

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 each parameter already has a detailed description including applicable sections and pagination behavior. The tool description adds minimal new parameter meaning—it provides high-level context about the sections themselves (e.g., what each section contains) but does not go beyond what the schema already documents for the parameters. The description's mention of 'opaque cursors' and page-number pagination is echoed in the schema. Baseline 3 is appropriate given the thorough 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 opens with a clear statement of purpose: 'Get the current profile for a PRIVATE foundation by EIN.' This identifies the specific verb, resource type, and required identifier, and distinguishes it from sibling search tools like search_foundations by emphasizing the single-foundation, profile-focused scope. It also outlines the various sections (public_profile, grant_history, etc.), further clarifying what the tool returns.

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 provides clear context on when to use the tool: for private foundations only (990-PF filers), covering specific tax years, and not counting toward monthly searches. It also notes that certain sections require Plus/Pro tiers, implying usage constraints. However, it does not explicitly name alternatives like search_foundations for broad queries, nor does it state when NOT to use this tool, though the exclusivity to private foundations implicitly guides selection.

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

All FundingLandscape 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?