Skip to main content
Glama

Nih Funding Concentration

nih_funding_concentration
Read-onlyIdempotent

Summarize NIH award dollars and record counts by fiscal year, recipient organization, contact PI, activity code, and funding mechanism for a bounded topic, organization, or PI search. Results disclose truncation and represent reported federal obligations, not valuation, revenue, or total research spending.

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": {
      "query": "gene therapy",
      "to_fiscal_year": 2026,
      "from_fiscal_year": 2022
    },
    "name": "nih_funding_concentration"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
pi_nameNo
organizationNo
to_fiscal_yearNo
from_fiscal_yearNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, open-world, and non-destructive behavior. The description adds valuable semantic disclosure beyond annotations: results may be truncated and represent reported federal obligations rather than valuation, revenue, or total research spending.

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 with no wasted wording. The tool's purpose and key output caveat are front-loaded efficiently.

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?

The description explains what is summarized and includes an important data-interpretation caveat, which helps because there is no output schema. However, for a five-parameter tool with no schema descriptions and no required parameters, it leaves too much unexplained about fiscal-year bounds and parameter behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for five undocumented parameters. It conceptually maps query, organization, PI, and fiscal year, but gives no detail on from_fiscal_year versus to_fiscal_year, accepted formats, defaults, or how the five parameters combine.

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?

The description uses a specific verb, 'Summarize,' and names the exact resource and aggregation dimensions: NIH award dollars and record counts by fiscal year, recipient organization, contact PI, activity code, and funding mechanism. This clearly distinguishes the tool as an aggregation tool for bounded searches rather than an award-history or project-lookup tool.

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 states the tool is for 'a bounded topic, organization, or PI search,' which gives implied usage context. However, it does not explicitly say when to use this versus siblings such as nih_grant_award_history or nih_reporter_get_project, nor does it state exclusions or prerequisites.

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.