Skip to main content
Glama

Nih Grant Award History

nih_grant_award_history
Read-onlyIdempotent

Build the annual NIH award history for one core project number, including award, direct/indirect cost, budget dates, application type, and cumulative reported funding. Annual award amounts are obligations for each fiscal year, not company revenue, cash received, or guaranteed 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": {
      "core_project_num": "UG1HD078437"
    },
    "name": "nih_grant_award_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
core_project_numYesCore project number, e.g. R43GM128494 or UG1HD078437.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful domain context that annotations cannot convey: annual award amounts are per-fiscal-year obligations, not revenue or guaranteed future funding. It says nothing about response ordering, pagination, or behavior when a project number has no history.

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 action and scope, with the caveat placed second. Every clause carries information an agent would otherwise have to guess, and nothing is repeated from the schema or annotations.

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?

With no output schema, the description usefully enumerates the fields returned and warns about the meaning of award amounts, which is the main interpretive trap for this data. Remaining gaps are minor: no note on how multi-year histories are ordered or how to distinguish competing awards for the same project.

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 schema supplies a concrete example format, so the parameter is already well documented. The description reinforces that exactly one core project number is expected rather than a list, which is a small but real addition beyond the schema; no format or normalization rules are added.

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 ('Build the annual NIH award history') scoped to 'one core project number' and enumerates the returned content (award, direct/indirect cost, budget dates, application type, cumulative reported funding). It is clear what the tool does, though it never names or contrasts a sibling such as nih_reporter_get_project, leaving that differentiation to the agent.

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?

'For one core project number' implies this is the single-project drill-down tool, so usage context is implied rather than stated. There is no explicit when-to-use/when-not guidance and no pointer to alternatives for multi-project or aggregate queries, which the sibling set clearly contains.

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.