Skip to main content
Glama

PubMed search: matching articles with PMID, title, authors

health_pubmed_abstracts
Read-only

PubMed search (NCBI E-utilities): matching articles with PMID, title, authors, journal, publication date and DOI. Citation metadata only, no abstract text. Up to 20 results. 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": "health_pubmed_abstracts"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesPubMed search terms, 2 to 200 characters
maxNoHow many results, 1 to 20 (default 5)

Output Schema

NameRequiredDescriptionDefault
queryNo
totalNo
sourceNo
resultsNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only cover readOnlyHint and openWorldHint, and the description adds genuinely new behavioral information: a hard cap of 20 results, a $0.002 per-call price, the x402/USDC payment mechanism across multiple networks, and that failed calls are not charged. This is exactly the payment/auth/limit context annotations cannot express, though it says nothing about rate limits or pagination.

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?

Three sentences, front-loaded with what the tool returns and what it excludes, then limits, then pricing. Slightly dense in the payment clause ('USDC on Base, Solana and 10 more networks'), which is more network detail than most agents need, but 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?

An output schema exists, so return-value explanation is optional, yet the description still previews the returned fields. With only two documented parameters, annotations covering safety, and payment terms disclosed, the definition is sufficient to invoke correctly; only rate-limit and error-behavior detail are absent.

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% and both parameters (q, max) are documented with ranges in the schema itself. The description only restates the upper bound ('Up to 20 results') without adding query syntax or formatting guidance, so baseline 3 applies.

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?

Names a specific resource and backend ('PubMed search (NCBI E-utilities)') and enumerates exactly what is returned: PMID, title, authors, journal, publication date and DOI. The clause 'Citation metadata only, no abstract text' actively distinguishes this from an abstract-returning search, so an agent can select it 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?

Usage is implied rather than stated: 'Citation metadata only, no abstract text' signals when this tool is and isn't appropriate, but there is no explicit when-to-use, no prerequisites, and no named alternative for full-text/abstract needs.

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