Skip to main content
Glama

Search Grants

search_grants
Read-onlyIdempotent

Search NIH-funded research projects. Filter by free-text query (topic/subject matter, matches title/abstract/terms, NOT the awardee), PI name, organization (the funded company/university/institution, use THIS, not query, for "what grants has <company/university> received"), fiscal year, US state, or NIH institute code (NCI, NHLBI, NIAID, etc.). Returns project number, PI, institution, fiscal year, award amount, and abstract preview.

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": {
      "ic": "NCI",
      "limit": 25,
      "query": "cancer immunotherapy",
      "fiscal_year": 2024
    },
    "name": "search_grants"
  }
}

Input Schema

NameRequiredDescriptionDefault
icNoNIH Institute/Center code (e.g., "NCI", "NHLBI", "NIMH")
limitNoResults per page (1-500, default 25)
queryNoFree-text search over project title/abstract/terms, an AND match on the SUBJECT MATTER words you pass (e.g. "cancer immunotherapy"), not a lookup by funding recipient. Do NOT put a company, institution, or organization name here: the name rarely appears verbatim in grant text, so it instead AND-matches on the name's individual common words and can return thousands of unrelated grants. For "what NIH grants has <company/university/institution> received", use `organization` instead.
stateNoUS state code (e.g., "CA")
offsetNoPagination offset (default 0)
pi_nameNoPI last name (or any name part)
fiscal_yearNoFiscal year (e.g., 2024)
organizationNoThe funded organization, the company, university, hospital, or institution that RECEIVED the award (e.g., "Stanford University"). This is the correct filter whenever the question names a specific organization/company/institution as the funding recipient, use it INSTEAD of `query`, which searches grant CONTENT, not the awardee.

Output Schema

NameRequiredDescriptionDefault
totalYesTotal number of matching grants
grantsYesArray of grant records
returnedYesNumber of grants returned in this response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / organization / description
      Previous value: -"The funded organization — the company, university, hospital, or institution that RECEIVED the award (e.g., \"Stanford University\"). This is the correct filter whenever the question names a specific organization/company/institution as the funding recipient — use it INSTEAD of `query`, which searches grant CONTENT, not the awardee."New value: +"The funded organization, the company, university, hospital, or institution that RECEIVED the award (e.g., \"Stanford University\"). This is the correct filter whenever the question names a specific organization/company/institution as the funding recipient, use it INSTEAD of `query`, which searches grant CONTENT, not the awardee."
    • changedInput schema / properties / query / description
      Previous value: -"Free-text search over project title/abstract/terms — an AND match on the SUBJECT MATTER words you pass (e.g. \"cancer immunotherapy\"), not a lookup by funding recipient. Do NOT put a company, institution, or organization name here: the name rarely appears verbatim in grant text, so it instead AND-matches on the name's individual common words and can return thousands of unrelated grants. For \"what NIH grants has <company/university/institution> received\", use `organization` instead."New value: +"Free-text search over project title/abstract/terms, an AND match on the SUBJECT MATTER words you pass (e.g. \"cancer immunotherapy\"), not a lookup by funding recipient. Do NOT put a company, institution, or organization name here: the name rarely appears verbatim in grant text, so it instead AND-matches on the name's individual common words and can return thousands of unrelated grants. For \"what NIH grants has <company/university/institution> received\", use `organization` instead."
  2. Changed2 schema fields changed
    • changedInput schema / properties / organization / description
      Previous value: -"Institution name (e.g., \"Stanford University\")"New value: +"The funded organization — the company, university, hospital, or institution that RECEIVED the award (e.g., \"Stanford University\"). This is the correct filter whenever the question names a specific organization/company/institution as the funding recipient — use it INSTEAD of `query`, which searches grant CONTENT, not the awardee."
    • changedInput schema / properties / query / description
      Previous value: -"Free-text search across title, abstract, terms"New value: +"Free-text search over project title/abstract/terms — an AND match on the SUBJECT MATTER words you pass (e.g. \"cancer immunotherapy\"), not a lookup by funding recipient. Do NOT put a company, institution, or organization name here: the name rarely appears verbatim in grant text, so it instead AND-matches on the name's individual common words and can return thousands of unrelated grants. For \"what NIH grants has <company/university/institution> received\", use `organization` instead."
  3. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "fiscal_year": 2024,
      +    "ic": "NCI",
      +    "limit": 25,
      +    "query": "cancer immunotherapy"
      +  },
      +  {
      +    "limit": 50,
      +    "organization": "Stanford University",
      +    "pi_name": "Smith",
      +    "state": "CA"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "grants": {
      +      "description": "Array of grant records",
      +      "items": {
      +        "properties": {
      +          "appl_id": {
      +            "description": "NIH application ID",
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "award_amount": {
      +            "description": "Total award amount in dollars",
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "award_notice_date": {
      +            "description": "Award notice date",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "contact_pi": {
      +            "description": "Contact principal investigator name",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "core_project_num": {
      +            "description": "Core project number",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "fiscal_year": {
      +            "description": "Fiscal year of award",
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "nih_institute": {
      +            "description": "NIH Institute/Center abbreviation or code",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "nih_institute_name": {
      +            "description": "Full name of NIH Institute/Center",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "org_city": {
      +            "description": "Organization city",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "org_country": {
      +            "description": "Organization country",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "org_state": {
      +            "description": "Organization state code",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "organization": {
      +            "description": "Organization/institution name",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "pis": {
      +            "description": "List of principal investigator names",
      +            "items": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "type": "array"
      +          },
      +          "project_end": {
      +            "description": "Project end date",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "project_num": {
      +            "description": "Project number",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "project_start": {
      +            "description": "Project start date",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "reporter_url": {
      +            "description": "Direct link to project on NIH Reporter",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "terms_preview": {
      +            "description": "Preferred terms/keywords preview",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "title": {
      +            "description": "Project title",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "returned": {
      +      "description": "Number of grants returned in this response",
      +      "type": "number"
      +    },
      +    "total": {
      +      "description": "Total number of matching grants",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "total",
      +    "returned",
      +    "grants"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety and idempotency need no restating. The description adds one genuinely behavioral detail — that a query match is an AND over subject-matter words and can return thousands of unrelated grants — but says nothing about result ordering, pagination behavior (limit/offset caps), or rate limits.

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 sentences, front-loaded with purpose then filters, then return fields; the parenthetical correctly placed next to 'organization' is where an agent will look. Slight redundancy with the schema's own query guidance costs it the top mark, but nothing is wasted.

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 all 8 parameters documented at 100% coverage, rich annotations, and an output schema, the description only needs to frame scope and the query/organization trap, which it does. Coverage of pagination/limit interaction and expected result volume is the only meaningful 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 description coverage is 100%, including a long explanation of query vs organization, so the schema already carries the semantics and the description's version is largely a restatement. It correctly reinforces the query/organization distinction and names the ic examples (NCI, NHLBI, NIAID), but adds no syntax, format, or default behavior the schema lacks — baseline 3.

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 and resource ('Search NIH-funded research projects') and immediately enumerates the filterable dimensions, which lets an agent separate this from publication-oriented or award-history siblings. It also carves out the scope boundary that the free-text query is not an awardee 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 routing rule with a quoted user phrasing: for 'what grants has <company/university> received' use organization, not query. That is a concrete when-to-use condition tied to a real failure mode. It stops short of saying when to prefer this tool over adjacent NIH tools such as award history or new-award tools, so no exclusions are stated.

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.