Skip to main content
Glama

Search PubMed articles by words and year

pubmed
Read-only

PubMed articles matching words, optionally from a year: PMID, title, first five authors, journal, date, DOI and link. Two NCBI requests. Attribution: PubMed (NCBI). Information only, not medical advice. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "pubmed"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch words
fromNoFirst publication year, e.g. 2020
limitNo1 to 20 (default 10)

Output Schema

NameRequiredDescriptionDefault
queryNo
totalNo
sourceNo
articlesNo
checkedAtNo
disclaimerNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real behavioral context beyond them — two upstream NCBI requests per call, attribution requirements, an information-only disclaimer, and a cost model charging $0.002 only for successful calls. It does not mention rate limits or latency, which keeps it short of a 5.

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?

The first sentence front-loads what the tool does, followed by compact attribution, disclaimer, and pricing notes. Listing the returned fields (PMID, title, authors, journal, date, DOI, link) is somewhat redundant given an output schema exists, but it is brief and does not bloat the definition.

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 three-parameter search tool with full schema coverage, an output schema, and read-only annotations, the description covers cost, upstream request count, and disclaimer obligations that an agent could not otherwise know. The main omissions are result pagination/ordering behavior and guidance on sibling alternatives.

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 schema already documents q, from, and limit. The description only echoes the optional year filter and says nothing about limit or result ordering, so it adds minimal meaning beyond the schema — the baseline 3 applies.

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?

States a specific verb and resource ('PubMed articles matching words, optionally from a year') and the title reinforces it. An agent can tell this searches the PubMed corpus, but nothing in the text distinguishes it from sibling literature tools like pm_search, arxiv, or clinical_trials.

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 agent must infer that this is the tool for biomedical literature queries. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. versus pm_search), so tool selection across the large sibling list is left to inference.

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.

Resources