Skip to main content
Glama

補助雷達 Taiwan Grants

Expected next rounds

next_round_forecasts
Read-onlyIdempotent

Programmes whose next round is already listed, or can be placed in a month because at least two past rounds opened in it. An estimate says so (basis: estimate) and is not an announcement. Up to 10 rows an answer and 3 pages; 300 rows a day per address.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
basisNo
queryNoWords in the programme's title or funder.
marketNotw = Taiwan, us = United States, uk = United Kingdom, eu = European Union. Leave it out for this site's own: tw.
months_aheadNoHow far ahead to look; 6 unless you say.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so credit goes to what the description adds: page/row caps (10 rows per answer, 3 pages), a daily quota of 300 rows per address, and the important reliability caveat that estimate-basis rows are predictions rather than confirmed announcements. That is genuinely useful behavior beyond the 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, purpose first, caveat second, limits last, with no filler. The phrasing 'can be placed in a month because at least two past rounds opened in it' is dense and slightly cryptic, which costs a point, but overall it is efficiently front-loaded.

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 5-parameter read-only search tool with annotations and no output schema, the description covers what the result set contains, how estimates are marked, and the paging/quota ceiling. The remaining gap is the shape of returned rows (fields, ordering), which an agent must discover by calling.

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 coverage is 60%, with market, months_ahead and query already described in the schema. The description adds real meaning for 'basis' by linking estimate to non-announcement status, but says nothing about page, market scoping, or how months_ahead interacts with the estimate logic. It compensates partially, not fully.

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 resource and scope: programmes whose next round is either already listed or statistically predictable from at least two prior rounds opening in the same month. The forecast/estimate framing is clear. It does not name or differentiate itself from siblings like upcoming_deadlines or search_open_grants, whose scope could overlap with 'next round is already listed'.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no named alternative. An agent cannot tell from the text whether to call this or upcoming_deadlines for a known deadline, or search_open_grants for currently fundable calls. The only guidance offered is interpretive ('an estimate is not an announcement'), not selection guidance.

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