Skip to main content
Glama

AY 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: us, uk, eu.
months_aheadNoHow far ahead to look; 6 unless you say.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 behavior, so the description is not needed for the safety profile. It adds genuinely useful operational facts the annotations do not carry: 10 rows per answer, a 3-page ceiling, a 300-rows-per-day-per-address rate limit, and the caveat that an estimated round is not an announcement. Return field contents are still undefined.

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 compact sentences, each carrying distinct information: the selection rule, the estimate caveat, and the limits. The opening sentence is somewhat convoluted ('can be placed in a month because at least two past rounds opened in it') but the substance is front-loaded with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, five-parameter list tool with no output schema, the definition covers the selection rule and the quota/pagination limits. It omits what a returned row contains (programme, funder, month, basis flag) and how listed versus estimated rows are distinguished in the payload, which the agent would need to interpret results.

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 descriptions already on query, market, and months_ahead. The description adds real meaning only for basis (estimate vs. listed, and that estimates are not announcements) and implicitly for page (3-page cap). It says nothing about the query or market parameters beyond the schema, so it neither compensates fully nor is silent.

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 names the resource precisely: programmes whose next round is already listed, or which can be projected from at least two past rounds in the same month. That is a concrete, verifiable selection rule rather than a restatement of the name. It does not, however, contrast itself with plausible siblings such as upcoming_deadlines or search_open_grants, so the agent must infer 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 the data rule (use this for forward-looking round timing, including estimated rounds), and the basis note tells the agent how estimates are produced. There is no explicit when-to-use or when-not-to-use statement and no named alternative, so the agent gets context but no routing 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