Skip to main content
Glama

search_pubmed_papers

Search PubMed and Europe PMC for biomedical papers and preprints, returning identifiers, abstracts, citations, grants, and open-access links for literature reviews and evidence gathering.

Instructions

Search 37,000,000+ biomedical papers & preprints via official EMBL-EBI Europe PMC & PubMed REST API (returns PMID/PMCID/DOI, full abstract, citations, author emails, MeSH terms, NIH/EU grants & free PDF URL).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_pubmed_papers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax papers (1 to 25, default 5).
queryNoKeywords, drug, disease, or PMID/DOI (e.g. 'GLP-1 semaglutide', 'CRISPR').
journalNoOptional journal name or ISO abbreviation (e.g. 'Lancet', 'N Engl J Med').
sort_byNorelevance (default), date, or cited.relevance
pub_year_fromNoOptional start publication year (e.g. 2023).
open_access_onlyNoRestrict to Open Access papers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does useful work by declaring provenance (official Europe PMC & PubMed REST API) and enumerating what comes back (PMID/PMCID/DOI, abstract, citations, author emails, MeSH terms, grants, PDF URL), but it says nothing about rate limits, authentication, pagination, ranking behavior, or what an empty/error result looks like.

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?

A single front-loaded sentence leads with the verb and corpus size, then packs return fields into a parenthetical. It is dense but every clause adds information, and the payload enumeration earns its place because no output schema exists. Minor cost: the long parenthetical is harder to scan than a short sentence plus a list.

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 six-parameter search tool with no output schema, the definition covers purpose, data source, scale and return fields, and the 100%-covered schema handles the parameters. Gaps remain around pagination/cursor behavior, maximum retrievable results, and whether repeated calls are needed for deeper result sets.

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%, with every parameter documented inline including examples and defaults, so the baseline is 3. The description itself adds no parameter-level meaning beyond restating the return payload; it never explains interactions such as how query handles a PMID/DOI versus keywords, or how sort_by='cited' relates to the limit.

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 names a specific verb (Search) and resource (biomedical papers & preprints) plus the corpus scale (37,000,000+) and the underlying sources (EMBL-EBI Europe PMC & PubMed REST API). The resource is unambiguously distinct from the sibling tools, which cover clinical trials, tenders, companies and NPI providers.

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?

Usage is only implied: the query parameter examples ('GLP-1 semaglutide', 'CRISPR') signal it is for literature/keyword lookups, but there is no explicit when-to-use guidance, no statement of when to prefer a different tool, and no note on when to add journal or year filters versus leaving them unset.

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