Skip to main content
Glama

AY Grants

Search open grants

search_open_grants
Read-onlyIdempotent

Grants open now or opening soon, soonest deadline first. Needs at least one of query, applicant, region or closes_within_days: there is no list of everything. Up to 10 rows an answer and 3 pages; 300 rows a day per address. Each row has our page (page_url) and the official notice (official_url).

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

Input Schema

NameRequiredDescriptionDefault
pageNo
queryNoWords in the title or the funder's name.
marketNotw = Taiwan, us = United States, uk = United Kingdom, eu = European Union. Leave it out for this site's own: us, uk, eu.
regionNoA Taiwan county or city (market tw) or a UK nation (market uk). Grants open to the whole country count too.
statusNoopen (the default) includes grants with no fixed deadline.
applicantNoWho can apply, as the list records it. Taiwan: 個人, 企業, 團體, 學校, 法人, 政府機關, 原住民, 農漁民. Elsewhere: Business, Nonprofits, Education, Government, Tribal, Individuals.
closes_within_daysNoOnly open grants whose deadline is in this many days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/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), and the description adds operational facts those annotations cannot carry: 10 rows per answer, 3 pages, and a 300-row-per-day quota tied to the caller's address. It also states the row payload includes page_url and official_url, so the agent knows where results point.

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?

Four compact sentences, front-loaded with what the tool returns and ordered by constraint, then limits, then row shape. Every clause carries a fact an agent needs, with no filler or restatement of the title.

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?

For a seven-parameter, read-only search tool with no output schema, the definition covers the essential gaps: the mandatory-filter rule, result ordering, pagination ceiling, quota, and two named response fields. It stops short of describing the remaining row fields or how the three-page window is traversed, which leaves a small residual gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 86%, so the baseline is 3, but the description adds a constraint the schema cannot express: not one of the seven parameters is marked required in the schema, yet at least one filter must be supplied. It also groups four of the filters as the qualifying set, which clarifies their relative role even though market, status and page are left to 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 opening sentence names the resource precisely (open / opening-soon grants) and the ordering (soonest deadline first), which is more than a restated name. It implicitly separates itself from a browse-all tool by stating what it returns, but it never names a sibling such as screen_grants or upcoming_deadlines, so routing still relies partly on inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a strong positive condition: at least one of query, applicant, region or closes_within_days must be supplied, and explains why ("there is no list of everything"). That is real usage guidance the schema does not express, but there is no explicit statement of when a sibling like screen_grants or get_grant would be the better choice.

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