Skip to main content
Glama

Nih Reporter Get Project

nih_reporter_get_project
Read-onlyIdempotent

Fetch one NIH project application record by application ID (numeric, distinct from project number). Returns its complete abstract, public-health relevance, terms, PIs, organization, dates, and award amount. Use nih_grant_award_history for multi-year award history.

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": {
      "appl_id": 10812345
    },
    "name": "nih_reporter_get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
appl_idYesNIH application ID (integer)

Output Schema

NameRequiredDescriptionDefault
pisYesList of principal investigator names
termsYesComplete terms/keywords for project
titleYesProject title
appl_idYesNIH application ID
abstractYesFull project abstract text
org_cityYesOrganization city
org_stateYesOrganization state code
contact_piYesContact principal investigator name
fiscal_yearYesFiscal year of award
org_countryYesOrganization country
project_endYesProject end date
project_numYesProject number
award_amountYesTotal award amount in dollars
organizationYesOrganization/institution name
reporter_urlYesDirect link to project on NIH Reporter
nih_instituteYesNIH Institute/Center abbreviation or code
project_startYesProject start date
terms_previewYesPreferred terms/keywords preview
core_project_numYesCore project number
award_notice_dateYesAward notice date
nih_institute_nameYesFull name of NIH Institute/Center
public_health_relevanceYesPublic health relevance statement

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so safety is covered. The description adds that the returned abstract is complete and enumerates the record's content (public-health relevance, terms, PIs, organization, dates, award amount), which tells an agent what depth of data to expect. No auth or rate-limit context is given, but that is a minor omission for a read-only lookup.

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: what it returns, what the record contains, and the alternative to use instead. Identity disambiguation is front-loaded and nothing is repeated.

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?

An output schema exists, so return-value documentation is not required, yet the description still summarizes the payload's richness. Combined with ID disambiguation and a named alternative, an agent has everything needed to select and call this single-parameter tool correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description earns above that by clarifying the identifier is numeric and distinct from a project number — a real disambiguation risk for NIH data that the schema's 'NIH application ID (integer)' does not fully guard against.

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?

States a specific verb (fetch) and resource (one NIH project application record), and explicitly scopes cardinality to a single record keyed by application ID. It also disambiguates the identifier from a project number, so an agent knows exactly what this tool targets versus a broader grant lookup.

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

Usage Guidelines4/5

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

Gives an explicit alternative and its selection condition: use nih_grant_award_history for multi-year award history. The single-record framing also implies it is not a search/list tool. It stops short of stating when-not to use it (e.g., searching by PI or organization), so it is strong but not exhaustive.

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.