Skip to main content
Glama

補助雷達 Taiwan 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: tw.
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.2/5.0
Behavior5/5

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

Goes well past the annotations (which only declare a safe, idempotent, closed-world read) by disclosing result ordering, page size (10 rows), a 3-page cap, a 300-rows-per-day-per-address budget, and the two link fields each row carries. Rate limits and pagination ceilings are exactly the behavior an agent cannot get from structured fields.

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 short sentences, front-loaded with scope and ordering before constraints, limits and return shape. Every sentence carries information an agent would otherwise have to discover by trial.

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?

With no output schema, the description compensates by naming the returned link fields, and it covers the two failure modes an agent would hit: an unfiltered query and exhausting the daily quota. Nothing needed to call it correctly appears to be missing.

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 baseline is 3, and the description earns above it by stating the cross-parameter requirement that no single field is mandatory in the schema but at least one of four must be supplied. It adds nothing about market, status or page semantics, but those are already documented in 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?

States the resource and scope precisely ('Grants open now or opening soon, soonest deadline first'), which tells an agent exactly what comes back and in what order. It does not name or differentiate itself from siblings like screen_grants or upcoming_deadlines, so it stops short of a 5.

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?

Gives a hard calling constraint: at least one of query, applicant, region or closes_within_days is needed because 'there is no list of everything' — this prevents a wasted browse call. It offers no guidance on when to pick this over screen_grants, get_grant or upcoming_deadlines, leaving sibling selection to inference.

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