Skip to main content
Glama

Search funding opportunities with full details

search_opportunities_full
Read-onlyIdempotent

Search Raise Lens grants and tenders and return full records: funder, description, eligibility, key requirements, source, apply link and the raiselens.com page. Up to 50 results a page; pass next_cursor back as cursor for the next page (first 1000 matches).

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_opportunities_full"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNogrant, tender, or any (both).any
limitNoResults per page.
queryNoSearch terms: what the project needs funding for.
cursorNoThe next_cursor value from the previous page.
sectorsNoRaise Lens sector slugs, such as renewable-energy. The first is used as a filter.
geographyNoISO-2 ("DE"), English name ("Germany") or aggregate ("EU").
deadline_beforeNoOnly opportunities closing on or before this date (YYYY-MM-DD).

Output Schema

NameRequiredDescriptionDefault
noteYes
pageYes
totalYesMatches in total.
resultsYes
next_cursorYesPass back as cursor for the next page; null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sectors / description
      Previous value: -"Sector slugs from list_sectors. The first is used as a filter."New value: +"Raise Lens sector slugs, such as renewable-energy. The first is used as a filter."
  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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description adds real operational context on top: page size ceiling of 50 and, importantly, the 1000-match cap on the result window plus the next_cursor-to-cursor chaining convention. What is missing is any note on result ordering or what happens once the 1000-match window is exhausted.

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 purpose before mechanics, with no filler. The enumeration of returned fields is somewhat redundant given an output schema exists, which keeps it from a 5.

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 seven optional parameters, full schema coverage, an output schema and complete annotations, the description supplies the remaining operational facts an agent needs: page size limit, continuation mechanism, and result-window cap. Only the sibling-routing guidance and ranking behavior are absent.

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 is already documented, and the baseline of 3 applies. The description contributes only the cross-parameter pagination flow (next_cursor back into cursor) and the overall 1000-match bound; it does not clarify how query, sectors and geography combine.

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 and resource ('Search Raise Lens grants and tenders') plus the differentiating scope ('return full records'), and enumerates the fields returned. It never names the lighter sibling search_opportunities, so the contrast with it is left implicit, but an agent can still infer that this variant is the detail-heavy one.

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: the 'full records' framing suggests picking this over a lite search, and the pagination sentence explains how to continue a result set. There is no explicit when-to-use or when-not guidance, and no named alternative, so the agent must infer the routing decision from the sibling name alone.

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