Skip to main content
Glama

補助雷達 Taiwan Grants

Upcoming deadlines

upcoming_deadlines
Read-onlyIdempotent

Open grants closing in the next days (14 unless you say, 30 at most), soonest first. 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": "upcoming_deadlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
pageNo
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.
applicantNoWho can apply, as the list records it. Taiwan: 個人, 企業, 團體, 學校, 法人, 政府機關, 原住民, 農漁民. Elsewhere: Business, Nonprofits, Education, Government, Tribal, Individuals.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds genuinely useful operational context absent from structured fields: a per-answer row cap (10), a page cap (3), and a rate limit of 300 rows/day per address, plus the 14-day default versus 30-day ceiling.

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 short sentences, no filler. Ordering and defaults come first, limits second — exactly the information an agent needs before calling.

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 five-parameter, all-optional list tool with no output schema, the definition covers ordering, default window, pagination and rate limits. It does not indicate what a row contains, which the absent output schema would otherwise have to carry, but the core invocation behavior is fully specified.

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%, above the baseline threshold, and the enums for market, region and applicant are self-documented. The description adds the non-schema default for days (14) and ties the 10-rows/3-pages limits to the page parameter, but says nothing about how market/region/applicant interact beyond what the schema states.

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 a specific resource and scope: 'Open grants closing in the next days', plus sort order ('soonest first'). An agent can distinguish this from a broad search, though no sibling is named explicitly to sharpen the boundary.

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 by phrasing ('open grants closing in the next days') and by the 14-day default, which suggests a deadline-tracking use case. No explicit when-not-to-use guidance or pointer to alternatives like search_open_grants or get_grant.

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