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. Individual grant recipients are never named: a recipient is named only when the IRS Business Master File confirms an organization of that name in that state, and a grant purpose that may name a person is withheld. 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

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

A3.9/5.0

Behavior5/5

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

With annotations already covering readOnly/idempotent/non-destructive, the description goes well beyond them: QA-gated filing-scoped facts, responsible-use limits on leadership data, the rule that individual grant recipients are never named unless the IRS BMF corroborates the organization, and intentional withholding of person-naming grant purposes. It also discloses quota treatment ('does not count toward your monthly searches').

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?

Purpose is front-loaded in the first sentence and the paragraph has no throwaway sentences, but it is dense compliance/policy prose rather than scannable structure, making it longer than the invocation task strictly requires.

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?

For a 12-parameter tool with no output schema, the description correctly explains what each section returns and the privacy boundaries, which is valuable. However it does not describe pagination/cursor behavior or error conditions (private-foundation-only rejection) that an agent would need for multi-page section retrieval.

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 100%, so the baseline is 3, but the description adds genuine meaning the schema does not: it explains the tier semantics behind the section enum (grant_history/repeat_grantees = Plus, leadership/federal_connections = Pro) and reinforces what each section returns. Most per-parameter syntax (page, cursor, state filters) is still handled by the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence gives a specific verb+resource: retrieving the current profile of a PRIVATE foundation by EIN. It also pins the eligible population (990-PF filers only) and scope (tax years 2018-2026). It never names or contrasts a sibling such as search_foundations, so the distinction from search-by-criteria is left implicit.

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?

Usage is implied rather than stated: the agent infers you call this when you already hold an EIN and want detail, and the description notes which sections require Plus vs Pro. There is no explicit 'use this instead of X when...' rule, and tier gating is also documented in the schema, so added guidance is thin.

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?