Skip to main content
Glama

Nih Reporter Search Publications

nih_reporter_search_publications
Read-onlyIdempotent

Search publications acknowledging NIH funding. Filter by PMID, application ID, or core project number. Useful for "what came out of this grant" follow-ups.

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": {
      "limit": 25,
      "appl_ids": "10812345,10812346"
    },
    "name": "nih_reporter_search_publications"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults per page (1-500, default 25)
pmidsNoComma-separated PubMed IDs
offsetNoPagination offset
appl_idsNoComma-separated NIH application IDs
core_project_numsNoComma-separated core project numbers (e.g., "R01CA123456")

Output Schema

NameRequiredDescriptionDefault
totalYesTotal number of matching publications
returnedYesNumber of publications returned in this response
publicationsYesArray of publication records

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, destructiveHint=false and openWorldHint=true, so the safety and idempotency profile is fully covered without the description. The description adds no behavior beyond that — no coverage of result ordering, empty-result behavior, or query cost for an open-world search — so it earns a baseline 3.

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 short sentences: purpose first, then the filter surface, then the use case. There is no filler, no restatement of the title, and the most decision-relevant information is front-loaded.

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?

For a read-only, open-world search with full schema coverage and a declared output schema, the description covers purpose, filter surface and a usage scenario adequately. Minor gaps remain around pagination expectations and how results are ordered, but nothing essential for correct invocation is missing.

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 every parameter (limit, offset, pmids, appl_ids, core_project_nums) carries its own description plus examples, so the schema does the heavy lifting. The description only restates which filter keys exist ('Filter by PMID, application ID, or core project number') without adding format or behavior detail, which matches the baseline 3 for high-coverage schemas.

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 ('Search publications acknowledging NIH funding') and enumerates the filter keys (PMID, application ID, core project number), so an agent knows exactly what corpus is being queried. It stops short of explicitly differentiating itself from look-alike siblings such as nih_grant_publication_summary or nih_reporter_get_project, so it lands at 4 rather than 5.

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?

The phrase 'Useful for "what came out of this grant" follow-ups' supplies a concrete usage scenario, which is better than nothing. However, no alternative tool is named and no exclusions are given, so an agent facing nih_grant_publication_summary has to infer which one to pick from names alone.

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.