Skip to main content
Glama

scan_pubmed_alerts

Scan PubMed for recent papers matching your research query and insert results as news briefs for daily review.

Instructions

Scan PubMed for recent papers matching a query.

Uses NCBI E-utilities (free, no API key required). Results are inserted
into news_briefs with source_type='article'. Safe to call daily from the
morning scan scheduler job.

Args:
    query: PubMed search query. Defaults to the query in user-preferences.json
           (pubmed_query field), then to your configured research field from
           user-config.yaml, then to a generic global-health fallback.
    reldate: Look back this many days (default: 1 = yesterday + today).
    max_results: Maximum papers to retrieve (default: 15).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
reldateNo
max_resultsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description fully discloses that it uses free NCBI E-utilities with no API key, inserts results into news_briefs, and is safe for daily scheduling. It does not detail rate limits or error handling, but the core behaviors are well explained.

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?

The description is concise and well-structured: a one-line summary, a context paragraph, and an Args list. Every sentence adds value without redundancy.

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?

Given the tool has an output schema, the description sufficiently covers inputs, data destination, and usage cadence. Missing details like error handling or rate limits are minor gaps, but the overall completeness is high for a simple scanning tool.

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?

The input schema has 0% description coverage, but the description's 'Args' section provides detailed semantics for each parameter: query's multi-level fallback, reldate's meaning, and max_results' default. This compensates entirely for the schema's lack of descriptions.

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 the tool 'Scan PubMed for recent papers matching a query', specifying the exact resource (PubMed) and action. It is distinct from siblings like scan_news or scan_openalex, which target different sources.

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 mentions it is 'Safe to call daily from the morning scan scheduler job', providing a clear use case. However, it does not explicitly state when not to use this tool or compare it to alternative scanning tools like scan_literature or scan_openalex.

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/SVerITG/Metis_PH'

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