Skip to main content
Glama

Nih Funding Expirations

nih_funding_expirations
Read-onlyIdempotent

Find active NIH projects matching a topic or organization whose current project period is scheduled to end soon. Treat the end date as a monitoring cue only, it can be extended, renewed, supplemented, or updated and does not prove a funding cliff.

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": 365,
      "organization": "New Echota Biotechnology"
    },
    "name": "nih_funding_expirations"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoForward window, 30-730 days (default 180).
limitNo1-100, default 25.
queryNo
organizationNo

Schema Changelog

Changes observed during successful MCP inspections.

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

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, open-world, non-destructive behavior, so the description needn't restate that. It instead adds genuine interpretive context: the end date is a monitoring signal and may be extended, renewed, supplemented, or updated — a meaningful caveat that prevents over-reading results. Return format and ordering are still undisclosed.

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 sentences, front-loaded with the operation and followed by the caution. No filler, and the most decision-relevant caveat is stated directly.

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?

All parameters are optional and the safety profile is covered by annotations, so the definition is nearly sufficient. The remaining gap is modest: how results are scoped or ordered and what a match on query actually covers, but nothing that would cause a wrong invocation.

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?

The phrasing 'matching a topic or organization' loosely maps to the query and organization parameters, and 'scheduled to end soon' maps to the days window. However, query and organization have no schema descriptions and the description does not clarify how matching works or how they interact, so it only partially compensates for 50% coverage.

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 gives a specific verb and resource: it finds active NIH projects filtered by topic or organization whose project period ends within a window. That is concrete enough to distinguish it from sibling list/search tools, though it never names or contrasts an alternative.

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?

It implies when the tool is relevant (monitoring projects approaching period end) and adds an interpretation rule — treat the end date as a cue, not proof of a funding cliff. It stops short of saying when to prefer this over related tools like new award or award-history lookups, so guidance remains implicit.

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.