Skip to main content
Glama

Search funding opportunities

search_opportunities
Read-onlyIdempotent

Search Raise Lens for sustainability funding opportunities (grants and tenders) by topic, sector, country and deadline. Returns up to 10 matches, each with title, summary, sectors, geography, deadline, amount and a link to the opportunity page on raiselens.com.

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

Input Schema

NameRequiredDescriptionDefault
typeNogrant, tender, or any (both).any
limitNoNumber of matches to return.
queryNoSearch terms: what the project needs funding for.
sectorsNoRaise Lens sector slugs, such as renewable-energy. Only the first is used as a filter; put the rest in `query`.
geographyNoCountry or region: ISO-2 ("DE"), English name ("Germany"), or an aggregate ("EU", "Global South").
deadline_beforeNoOnly opportunities closing on or before this date (YYYY-MM-DD).

Output Schema

NameRequiredDescriptionDefault
noteYesMatch count and what the records include.
resultsYes
signup_urlYes

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. Only the first is used as a filter; put the rest in `query`."New value: +"Raise Lens sector slugs, such as renewable-energy. Only the first is used as a filter; put the rest in `query`."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds a result cap ('up to 10 matches') and the reality that results link out to raiselens.com, which is mild added context. It omits ranking/ordering behavior, empty-result behavior, and the notable quirk that only the first sector is used as a filter.

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, with no filler. The second sentence partially duplicates the output schema by enumerating returned fields, which is the only slightly wasteful element.

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?

With an output schema present and rich annotations, the description need not explain return values or safety, and it correctly avoids doing so at length. The remaining gap is comparative positioning against close siblings like 'search_opportunities_full', which for a tool whose main risk is wrong-tool selection is a meaningful omission.

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 the parameters are already fully documented, including the caveat that only the first sector slug is used and the geography format options. The description's phrase 'by topic, sector, country and deadline' merely maps to the schema fields without adding syntax, defaults, or interaction guidance.

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 states a specific verb and resource ('Search Raise Lens for sustainability funding opportunities (grants and tenders)') and names the filterable dimensions, which is far more than a restatement of the name. It does not, however, differentiate itself from the sibling 'search_opportunities_full', which an agent could easily confuse with it.

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 query/sector/country/deadline framing suggests exploratory, filtered lookups, but there is no explicit when-to-use or when-not-to-use guidance. Nothing tells the agent why it should pick this over 'search_opportunities_full' or 'list_new_opportunities'.

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