Skip to main content
Glama

Nih Grant Publication Summary

nih_grant_publication_summary
Read-onlyIdempotent

Count publications linked by NIH RePORTER to a core project number and return a bounded PMID sample. Publication linkage reflects acknowledged grant support; it is not a citation-impact, product-readiness, or causal-attribution measure.

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,
      "core_project_num": "UG1HD078437"
    },
    "name": "nih_grant_publication_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPMID sample size, 1-100 (default 25).
core_project_numYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"PMID sample size, 1–100 (default 25)."New value: +"PMID sample size, 1-100 (default 25)."
  2. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the description's real contribution is the semantic caveat: linkage means acknowledged grant support, not citation impact, product readiness, or causal attribution. That is genuinely useful framing not available in structured fields, and the bounded-sample return shape is disclosed. It still does not say what happens for an unknown or unfunded core project number.

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 the action and return shape, followed by a scoping caveat. The triple negative list ('citation-impact, product-readiness, or causal-attribution') is slightly padded but each clause guards against a plausible misreading.

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?

For a two-parameter read-only counter this is nearly sufficient, but with no output schema the description should say more about the response shape (total count plus PMID list, and whether the count is capped by limit). Handling of an unmatched core project number is also unaddressed.

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 coverage is 50%: limit is fully documented in the schema (1-100, default 25), while core_project_num has no schema description. The description reinforces the project-number semantics but adds no format detail (the worked example UG1HD078437 lives in the schema, not the text). Baseline 3 is appropriate since the schema does most of the work.

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 states a specific verb pair (count + return a bounded PMID sample) and a specific resource (publications linked by NIH RePORTER to a core project number), so an agent can distinguish it from search-style siblings. It stops short of naming the closest sibling (nih_reporter_search_publications) to sharpen the boundary, but the counting-vs-listing distinction is implicit in the wording.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative; the only usage signal is the implied input (a core project number). An agent must infer from the name and siblings when to pick this over a publication search tool.

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.