Skip to main content
Glama

List new funding opportunities

list_new_opportunities
Read-onlyIdempotent

Grants and tenders added to Raise Lens since a date (up to 90 days back), newest first, as full records (funder, description, eligibility, source, apply link). Optional filters: sector slug, country, type. Paged: pass next_cursor back as cursor.

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

Input Schema

NameRequiredDescriptionDefault
typeNogrant, tender, or any (both).any
limitNoResults per page.
sinceNoYYYY-MM-DD. Defaults to 7 days ago.
cursorNoThe next_cursor value from the previous page.
sectorNoOne Raise Lens sector slug, such as renewable-energy.
countryNoISO-2, English name or aggregate.

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 / sector / description
      Previous value: -"One sector slug (list_sectors)."New value: +"One Raise Lens sector slug, such as renewable-energy."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds real behavioral context the annotations do not: the hard 90-day cap on 'since', newest-first ordering, and the paged-token workflow ('pass next_cursor back as cursor').

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?

Two dense sentences with no filler; the core scope constraint and ordering are front-loaded before the filter and pagination details, each of which earns its place.

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

Completeness5/5

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

For a 6-parameter read-only list tool with an output schema and full annotations, the description covers everything an agent needs: scope, cap, ordering, record richness, filters, and how to page.

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 schema already explains type, limit, since, cursor, sector and country. The description only restates that sector/country/type are optional filters and implies the cursor chaining, adding little meaning beyond the schema baseline of 3.

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+resource ('Grants and tenders added to Raise Lens') plus scope ('since a date, up to 90 days back'), ordering ('newest first') and payload shape ('full records'). It is clearly distinguishable from a search tool by its recency-anchored 'added since' framing, though it never names a sibling to route against.

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 implied rather than stated: the 90-day lookback and 'newest first' ordering signal a recency-discovery use case, but there is no explicit when-to-use, when-not, or named alternative such as the search_opportunities family for keyword lookups.

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