Skip to main content
Glama

AY 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: us, uk, eu.
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 cover safety (readOnly, idempotent, non-destructive, closed-world), yet the description adds genuinely non-obvious operational facts: 10 rows per answer, 3 pages maximum, and a 300-rows-per-day-per-address quota. That rate-limit and pagination disclosure is exactly the kind of context annotations cannot express, though it stops short of saying what a row contains.

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 the primary scope first, then limits and quota. No filler, and the default value is front-loaded before the cap.

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, zero-required read tool with no output schema, the description covers defaults, sort order, pagination and rate limits well. The remaining gap is that nothing describes what a returned row looks like, which matters slightly more given there is no output schema.

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?

With 60% schema coverage, the schema already documents the market, region and applicant enums in detail. The description adds real value only for 'days' (default 14, cap 30) and 'page' (3-page ceiling); it adds nothing about market/region interactions, so it neither compensates fully nor is redundant.

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 within a window, sorted soonest-first. An agent can tell this is a deadline-oriented list rather than a general search, though it never names the sibling search_open_grants or next_round_forecasts to sharpen the distinction.

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?

The default window (14 days, 30 max) is stated, which implies 'use this for short-horizon deadline checks', but there is no explicit guidance on when to prefer this over search_open_grants or next_round_forecasts. Usage is implied rather than directed.

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