Skip to main content
Glama

Get a funder with full details

get_funder_full
Read-onlyIdempotent

Fetch one Raise Lens funder by slug or raiselens.com/funders URL with full details: website and apply links, AUM or fund size, typical grant size, submission window, programmes and recent grants or investments, plus its name, type, sectors, geographic focus and cheque size. Never includes personal contact details.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url_or_slug": "<url_or_slug>"
    },
    "name": "get_funder_full"
  }
}

Input Schema

NameRequiredDescriptionDefault
url_or_slugYesA Raise Lens funder slug, or its raiselens.com/funders URL.

Output Schema

NameRequiredDescriptionDefault
urlNoThe funder page on raiselens.com.
nameNo
slugNoFunder id (slug) on Raise Lens.
foundYes
accessNoLevel of detail in this record: summary or full.
stagesNo
sectorsNo
websiteNo
categoryNoFunder type slug (foundation, climate-vc, dfi-sovereign...).
hq_countryNoHeadquarters country, ISO-2.
programmesNo
cheque_sizeNoUsual and largest ticket, in words (USD).
hq_locationNo
linkedin_urlNoThe organisation page.
aum_fund_sizeNo
funding_typesNo
next_deadlineNo
recent_grantsNoRecent grants or investments to organisations.
category_labelNo
application_urlNo
application_noteNoHow to approach or apply, as the funder describes it.
geographic_focusNoCountries and regions the funder states it covers.
submission_windowNo
open_to_applicationsNoyes, no or unknown, as the funder states it.
open_opportunity_countNoOpen grants and calls from this funder listed on Raise Lens.
typical_grant_size_max_usdNo
typical_grant_size_min_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / url_or_slug / description
      Previous value: -"A funder slug from search_funders, or its raiselens.com/funders URL."New value: +"A Raise Lens funder slug, or its raiselens.com/funders URL."
    • changedOutput schema / 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 this a safe, idempotent, closed-world read, so the description's job is to add context. It does so by enumerating the returned detail fields and, notably, stating 'Never includes personal contact details' — a genuine behavioral guarantee an agent could not infer from annotations alone.

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?

A single sentence, front-loaded with the verb, resource, and lookup key before the field enumeration. The field list is dense but each item is informative; minor bloat only in the tail ('cheque size' overlapping 'typical grant size').

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 an output schema present, the description need not explain return values, yet the field summary helps an agent judge whether this tool is worth calling. The only gap is the absence of any error behavior for an invalid slug or URL.

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?

There is a single parameter with 100% schema description coverage, and the description's 'by slug or raiselens.com/funders URL' merely restates the schema's own wording. No additional format examples or edge cases are provided.

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?

States a specific verb ('Fetch') and resource ('one Raise Lens funder') and adds scope ('full details'), which implicitly separates it from search_funders and the list_* siblings. It stops short of naming any sibling explicitly, so the differentiation is inferred rather than stated.

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 'one ... by slug or URL' framing implies use after you already have a specific funder identifier, but there is no explicit when-to-use or when-not-to-use guidance and no pointer to search_funders for discovery. Usage is only implied.

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