Skip to main content
Glama

pubmed_search

Search PubMed/MEDLINE by query or PMIDs to retrieve full article records, including titles, authors, journals, DOIs, MeSH terms, and abstracts.

Instructions

PubMed / MEDLINE search with full records: PMID, title, authors, journal, year, volume/pages, DOI, PMCID, publication types, MeSH terms and abstract. Accepts PubMed query syntax or a list of PMIDs. No API key needed. Costs 0.003 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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": "pubmed_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoPubMed query
maxNo1-20, default 5
pmidNoComma-separated PMIDs (alternative to q)
sortNorelevance or pub_date
abstractsNotrue/false, default true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the per-call cost and chain (0.003 USDC on Base, x402), that no API key is required, and the exact failure mode (402 challenge returned without a payment key). It omits rate limits, result caps, and error behavior beyond the 402 case.

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?

Front-loaded with purpose and return contents, then payment mechanics in two short sentences. Every clause earns its place; nothing is redundant.

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?

No output schema exists, so the enumeration of returned fields usefully substitutes for one, and the payment/auth story is fully covered. Minor gaps remain on result caps and non-402 error behavior for a five-parameter tool.

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%, so the baseline is 3. The description only restates that q takes PubMed syntax and pmid is an alternative, adding no format examples or constraints beyond what the schema already documents for q, max, sort, and abstracts.

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 ('PubMed / MEDLINE search') and enumerates exactly what comes back (PMID, title, authors, journal, DOI, MeSH, abstract). An agent can distinguish it from other retrieval tools 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 Guidelines3/5

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

Conveys the two input modes (query syntax vs. PMID list) and a hard prerequisite (a payment key), which is useful context. It never says when this tool is preferable to a sibling like arxiv_search, nor when not to use it; usage is only implied by the domain.

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