Skip to main content
Glama
u9401066

pubmed-search-mcp

by u9401066
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_article_references

Read-onlyIdempotent

Retrieve the bibliography of a PubMed article to find the papers it cites, supporting foundational research and source verification.

Instructions

Get the references (bibliography) of a PubMed article.

Returns the list of articles that this paper cites in its bibliography. This is the OPPOSITE of find_citing_articles:

  • get_article_references: Papers THIS article cites (backward in time)

  • find_citing_articles: Papers that cite THIS article (forward in time)

═══════════════════════════════════════════════════════════════ 📚 BACKWARD CITATION SEARCH (Foundation Discovery) ═══════════════════════════════════════════════════════════════

Direction: Source Paper → Papers it cited (BACKWARD in time)

USE CASES: ──────────

  • 🏛️ Find foundational papers: Core works the field builds on

  • ⚗️ Methodology sources: Papers describing techniques used

  • 📖 Background reading: Build understanding of a topic

  • 🔍 Verify claims: Check sources for specific assertions

═══════════════════════════════════════════════════════════════ EXAMPLE WORKFLOW: ═══════════════════════════════════════════════════════════════

Start with a recent review article

get_article_references(pmid="38123456", limit=50) → Get the bibliography of this review

Find most-cited foundational papers

get_citation_metrics(pmids="last", sort_by="citation_count") → Identify which references are the most influential

Read a foundational paper

fetch_article_details(pmids="12345678") → Get full details of an important reference

Args: pmid: PubMed ID of the source article ("12345678" or "PMID:12345678"). limit: Maximum number of references to return (1-100, default: 20).

Returns: List of referenced articles with details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pmidYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.7.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • removedInput schema / properties / pmid / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "integer"
-  }
-]
    • addedInput schema / properties / pmid / maxLength
      Added value: +512
    • addedInput schema / properties / pmid / minLength
      Added value: +1
    • addedInput schema / properties / pmid / type
      Added value: +"string"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_article_referencesOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.5.16

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuine context: the backward-in-time direction, that it returns a bibliography list, and the limit range. It stops short of describing ordering or pagination behavior, but the annotation coverage lowers the bar.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core definition is correctly front-loaded in the first three lines, but the rest is bloated with emoji banners, ASCII rules, and a multi-step workflow example that repeats usage information already stated. Much of the decoration does not earn its place.

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 two-parameter read tool with no output schema, the description covers purpose, direction, parameters, and usage adequately; the 'Returns' note is appropriately brief since it is itself a thin summary. Slightly more on result ordering or limit semantics would complete it.

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 description coverage is 0%, so the description must carry the load. It documents the pmid accepted formats ('12345678' or 'PMID:12345678') and the limit range/default, adding real meaning beyond the bare schema types. It could be slightly richer about what happens at the limit boundary, but it compensates well for the coverage gap.

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 ('Get the references of a PubMed article') and immediately distinguishes itself from the sibling find_citing_articles by contrasting citation direction. An agent can select this without opening the schema.

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

Usage Guidelines5/5

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

Explicitly names the alternative (find_citing_articles), gives the condition that selects each, and lists four concrete use cases. Nothing is left to inference about when to reach for this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools