Skip to main content
Glama

List research grants

list_grants
Read-onlyIdempotent

Use this when the user asks who funds work on a target, drug, process or lab, how much and since when. Aging research grants from NIH, the EU (CORDIS), UKRI and Wellcome, newest award first: title, funder, holder, investigators, amount, period and a link to the record. For company financings use list_news.

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

Input Schema

NameRequiredDescriptionDefault
qNoWords of the grant's title ("quoted phrases", OR and -exclusions work).
limitNoResults per page.
sinceNoOnly grants awarded on or after this date (YYYY-MM-DD).
untilNoOnly grants awarded on or before this date (YYYY-MM-DD).
cursorNoFrom the last page's `pagination.next_cursor`; keep the other arguments the same.
entityNoOnly grants whose titles name this entity, as `type:key` (from find_entities), e.g. `intervention:rapamycin` or `disease:sarcopenia`. A bare key works too.
funderNoOnly grants from this funder, by its organization key or name, e.g. `nia` or `wellcome`.
holderNoOnly grants held by this organization (its key) or investigator (`person:` and their key), e.g. `buck-institute-for-research-on-aging`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / entity / description
      Previous value: -"Only grants whose titles name this entity, as `type:key` (from find_entities), e.g. `intervention:rapamycin` or `disease:sarcopenia`."New value: +"Only grants whose titles name this entity, as `type:key` (from find_entities), e.g. `intervention:rapamycin` or `disease:sarcopenia`. A bare key works too."
    • removedInput schema / properties / entity / pattern
      Removed value: -"^[a-z]+:.+$"
  2. Changed1 schema field changed
    • changedInput schema / properties / entity / description
      Previous value: -"Only grants whose titles name this entity, as `type:key` (see /entities), e.g. `intervention:rapamycin` or `disease:sarcopenia`."New value: +"Only grants whose titles name this entity, as `type:key` (from find_entities), e.g. `intervention:rapamycin` or `disease:sarcopenia`."
  3. Changed2 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque cursor from `pagination.next_cursor` of the previous page. Keep the other parameters the same."New value: +"From the last page's `pagination.next_cursor`; keep the other arguments the same."
    • changedInput schema / properties / limit / description
      Previous value: -"Results per page, 1 to 25."New value: +"Results per page."
  4. Changed2 schema fields changed
    • changedInput schema / properties / funder / description
      Previous value: -"Only grants from this funder, by its organisation key or name, e.g. `nia` or `wellcome`."New value: +"Only grants from this funder, by its organization key or name, e.g. `nia` or `wellcome`."
    • changedInput schema / properties / holder / description
      Previous value: -"Only grants held by this organisation (its key) or investigator (`person:` and their key), e.g. `buck-institute-for-research-on-aging`."New value: +"Only grants held by this organization (its key) or investigator (`person:` and their key), e.g. `buck-institute-for-research-on-aging`."
  5. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuinely new context beyond them: the covered funder corpora, the deterministic newest-first ordering, and the shape of each record. It does not mention result caps, auth needs or freshness/lag of the underlying grant data, which keeps it below a 5.

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?

Three tight sentences: trigger, capability/ordering/return fields, then the sibling redirect. No filler, and the highest-value information (when to use) is front-loaded.

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?

For an 8-parameter, zero-required, read-only list tool with a fully documented schema and full annotation coverage, the description supplies everything an agent needs: the trigger, the corpora covered, the ordering, the record shape, and the disambiguation from list_news. The absence of an output schema is compensated by the inline field list.

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 description coverage is 100% and the parameter descriptions are already precise (entity format, cursor reuse instructions, funder/holder key conventions), so the schema carries the semantics. The description adds only loose framing ('who funds work on a target, drug, process or lab', 'how much and since when') that gestures at funder/holder/entity/date filters without adding syntax or constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the specific resource (aging research grants), the exact source corpora (NIH, EU CORDIS, UKRI, Wellcome), the sort order (newest award first), and the returned fields. It also explicitly contrasts itself with list_news for company financings, so an agent can route between them without opening either schema.

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

Usage Guidelines5/5

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

Opens with a concrete trigger phrase ('when the user asks who funds work on a target, drug, process or lab, how much and since when') and supplies an explicit redirect ('For company financings use list_news'). Both when-to-use and when-to-use-something-else are stated.

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.