Skip to main content
Glama

Nih New Grant Awards

nih_new_grant_awards
Read-onlyIdempotent

Find recently issued NIH awards, optionally restricted to new competing applications, topic, organization, state, institute, activity code, or SBIR/STTR. Useful for financing and emerging-program monitoring; an award notice does not establish commercial validation or future funding.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "days": 90,
      "query": "gene therapy",
      "new_competing_only": true
    },
    "name": "nih_new_grant_awards"
  }
}

Input Schema

NameRequiredDescriptionDefault
icNo
daysNoLook-back window, 1-365 days (default 30).
limitNo1-100, default 25.
queryNoTopic text across title, abstract, and terms.
stateNo
organizationNo
activity_codeNoNIH activity code such as R01, R43, or U01.
sbir_sttr_onlyNoRestrict to SBIR/STTR research projects.
new_competing_onlyNoRestrict to application type 1 (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / days / description
      Previous value: -"Look-back window, 1–365 days (default 30)."New value: +"Look-back window, 1-365 days (default 30)."
    • changedInput schema / properties / limit / description
      Previous value: -"1–100, default 25."New value: +"1-100, default 25."
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so safety is covered. The description adds genuine interpretive context beyond that: an award notice does not establish commercial validation or future funding, which guards against over-reading results. It does not discuss result volume or pagination, keeping it short of 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.

Conciseness4/5

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

Two compact sentences, front-loaded with purpose and filters, then a caveat. Every clause earns its place, though the filter enumeration is dense enough that it reads closer to a keyword list than prose.

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 nine-parameter, read-only search with no output schema, the definition covers what is searched, what can be filtered, the default look-back behavior implied by "recently," and a caution on interpretation. Return payload shape is not described, but the tool is simple enough that this is a minor gap.

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 67%, and the description maps several thin schema fields to meaning (institute for "ic", topic text for "query", SBIR/STTR, new competing applications). The remaining parameters (days, limit) are already documented in the schema, so the description adds moderate rather than decisive value.

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?

Uses a specific verb ("Find") with a scoped resource ("recently issued NIH awards") and enumerates the filterable dimensions. It implicitly contrasts with the historical sibling by emphasizing recency, but never names an alternative, so sibling differentiation is only inferred.

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 clause "Useful for financing and emerging-program monitoring" gives a use case, which is more than nothing, but there is no explicit when-to-use rule, no when-not condition, and no named alternative such as the award-history tool. An agent must guess which NIH tool fits a given question.

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.