Skip to main content
Glama

Search funders and investors

search_funders
Read-onlyIdempotent

Search the Raise Lens directory of sustainability funders and investors (foundations, climate VCs, corporate investors, development finance institutions, government funders) by topic, funder type, funding type and geography. Returns up to 20 funders ranked by relevance to the query, then by how many open opportunities each has on Raise Lens. Each has name, type, funding types, sectors, geographic focus, cheque size, next deadline, how to apply, open opportunity count and its raiselens.com page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_funders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of funders to return.
queryNoWhat the funder backs, e.g. "green hydrogen", "mangrove restoration", or a funder name.
categoryNoFunder type.
open_nowNotrue: only funders open to applications or with open opportunities listed.
geographyNoCountry or region: ISO-2 ("KE"), English name ("Kenya") or a region ("East Africa"). Matches funders based there or naming it in their focus.
funding_typeNogrant, equity, debt, guarantee or any. Matches what the funder states, or what its type implies when it states nothing.any

Output Schema

NameRequiredDescriptionDefault
noteYes
totalYesFunders matched before the limit.
resultsYes
plans_urlYesRaise Lens page that lists what each option includes; null when every record is full.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / results / items / properties / slug / description
      Previous value: -"Funder id on Raise Lens; pass to get_funder_full."New value: +"Funder id (slug) on Raise Lens."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: results are capped and ranked first by query relevance, then by count of open opportunities. The trailing field list is largely covered by the output schema, which keeps it from a 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?

Two sentences, front-loaded with what is searched and how results are ordered, with no filler. The second sentence's enumeration of returned fields duplicates the output schema, so it is padding rather than earning its place.

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?

With full parameter documentation, an output schema, and safety annotations, the description covers the mechanics an agent needs: scope, filters, ranking, and result cap. The only real omission is how this relates to get_funder_full when a follow-up lookup is needed.

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 every parameter's meaning is already documented, including default limit=10 and the ISO-2/English/region flexibility of geography. The description only restates the filter axes ('by topic, funder type, funding type and geography') and adds no matching syntax or tie-breaking detail beyond the schema.

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 description gives a specific verb and resource ('Search the Raise Lens directory of sustainability funders and investors') and enumerates the funder subtypes covered, so the entity searched is unmistakable. It never contrasts itself with the closest sibling, get_funder_full, so an agent cannot tell from the text alone when to search versus fetch a single funder by name.

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 only implied: an agent can infer this is the discovery entry point for funders, and the mention of topic/type/geography hints at browsing workflows. There is no explicit when-to-use statement, no when-not, and no routing to search_opportunities or get_funder_full for follow-up detail.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources