Skip to main content
Glama
u9401066

pubmed-search-mcp

by u9401066
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_fulltext

Retrieve fulltext of academic articles by searching multiple sources like Europe PMC, Unpaywall, and CORE. Accepts PMID, PMC ID, or DOI as input.

Instructions

🔥 Enhanced multi-source fulltext retrieval.

Automatically tries multiple sources to find the best fulltext:

  1. Europe PMC (if PMC ID available)

  2. Unpaywall (finds OA versions via DOI)

  3. Institutional direct/EZproxy fetch (when DOI-backed and enabled)

  4. CORE (200M+ open access papers)

With extended_sources=True, also searches: 5. CrossRef (publisher links) 6. DOAJ (Gold OA journals) 7. Zenodo (research repository) 8. PubMed LinkOut (external providers) 9. Semantic Scholar, OpenAlex, arXiv, bioRxiv, medRxiv

Accepts flexible input - provide ANY ONE of:

  • identifier: Auto-detects PMID, PMC ID, or DOI

  • pmcid: Direct PMC ID

  • pmid: PubMed ID (will lookup PMC ID)

  • doi: DOI (will search Unpaywall/CORE)

Args: identifier: Auto-detect format - PMID, PMC ID, or DOI Examples: "PMC7096777", "12345678", "10.1001/jama.2024.1234" pmcid: PubMed Central ID (e.g., "PMC7096777", "7096777") pmid: PubMed ID (e.g., "12345678") doi: DOI (e.g., "10.1001/jama.2024.1234") sections: Filter sections (e.g., "introduction,methods,results") include_pdf_links: Include PDF download links (default: True) include_figures: Include figure metadata with image URLs (default: False) extended_sources: Search the extended downloader chain after the standard policy (default: False) output_format: Response format - "markdown" (default), "json", or "toon" allow_browser_session: Control browser-session fallback. - True: force broker fallback when configured - False: disable broker fallback - None: use auto mode from broker configuration

Returns: Fulltext content with PDF links from all available sources.

Example: get_fulltext(identifier="PMC7096777") get_fulltext(doi="10.1038/s41586-021-03819-2") get_fulltext(pmid="12345678", extended_sources=True)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierNo
pmcidNo
pmidNo
doiNo
sectionsNo
include_pdf_linksNo
include_figuresNo
extended_sourcesNo
output_formatNomarkdown
allow_browser_sessionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It details the multi-source retrieval order, browser-session fallback, and return format. However, it omits potential rate limits or failure scenarios.

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?

Well-structured with clear sections and examples, but slightly verbose with some redundancy. Front-loaded with purpose, but could be trimmed.

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?

Covers all 10 parameters, multiple source methods, output formats, and provides examples. Comprehensive for the tool's complexity.

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

Parameters5/5

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

Schema has 0% description coverage; the description fully explains each parameter with examples and purpose, adding essential meaning beyond the schema.

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?

The description clearly states 'Enhanced multi-source fulltext retrieval' and lists multiple sources, distinguishing it from siblings like fetch_article_details or get_cached_article. It provides specific verb+resource and examples.

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 description explains flexible input and extended_sources but does not explicitly tell when to use this tool versus alternatives. It lacks exclusions or when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/u9401066/pubmed-search-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server