Skip to main content
Glama

FundingLandscape

by io.github.tettertotter
OverviewDiscussionsAdmin

Search Foundations

search_foundations
Read-onlyIdempotent

Look up a private foundation by full legal name or EIN in the active QA-gated Foundation Intelligence release (3,678 profiles). Covers IRS tax years 2018 to 2026. Mission/topic discovery and grant-purpose search are withheld until their source and quality contracts pass review. Counts toward your monthly searches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax foundations to return (default: 10, max: 50)
queryYesFull private-foundation legal name or 9-digit EIN. Examples: "Gates Foundation" or "56-2618866". Mission/topic queries are not available in this release.
statesNoFilter by state (2-letter codes). Where foundation is based.
min_annual_givingNoMinimum annual giving in dollars

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / include_grants
      Removed value: -{
-  "description": "Include similar historical grants (default: true)",
-  "type": "boolean"
-}
    • changedInput schema / properties / query / description
      Previous value: -"Natural language description of the work or mission. Example: \"youth education programs\""New value: +"Full private-foundation legal name or 9-digit EIN. Examples: \"Gates Foundation\" or \"56-2618866\". Mission/topic queries are not available in this release."
    • removedInput schema / properties / verbosity
      Removed value: -{
-  "description": "minimal=name/ein/giving, summary=+location/sectors/explanation, full=+grants/trends",
-  "enum": [
-    "minimal",
-    "summary",
-    "full"
-  ],
-  "type": "string"
-}
  2. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Natural language description of the work or mission. Examples: \"climate change initiatives in midwest\", \"youth education programs\", \"arts and culture in New York\""New value: +"Natural language description of the work or mission. Example: \"youth education programs\""
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds valuable behavioral context beyond those: the release is QA-gated, limited to 3,678 profiles, covers IRS tax years 2018–2026, and calls count against the monthly quota. It does not mention pagination or result shape, but the annotations carry the safety burden.

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?

Three sentences, all information-dense: main action, release scope, temporal coverage, explicit exclusions, and quota impact. The action is front-loaded and there is no filler or redundant phrasing.

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

Completeness4/5

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

The description covers the essential operation, constraints, exclusions, and quota. Since there is no output schema, it does not specify the exact result fields, and pagination is unspecified. Given the simple 4-param schema and annotations, it is substantively complete, though a sentence describing the return shape would improve it.

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 has 100% description coverage, so the baseline is 3. The description reinforces the two accepted query forms (full legal name or EIN) and the unavailability of mission/topic queries, which mostly duplicates schema text. It adds the tax-year coverage range, but that is not parameter-specific, so little extra meaning is added over the structured properties.

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 'look up', resource 'private foundation', and the lookup keys 'full legal name or EIN'. Explicitly narrows the scope to the QA-gated Foundation Intelligence release with 3,678 profiles, distinguishing it from sibling search tools that cover grants/procurement or mission/topic.

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 makes the exclusion clear ('Mission/topic discovery and grant-purpose search are withheld') and implies the tool is only for exact name/EIN lookup, but it does not name any alternative tool (e.g., funders_for_cause or find_funders_of) for those withheld use cases. Guidance on when to use this vs. siblings is implied rather than explicit.

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

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