Skip to main content
Glama

search_literature

Read-only

Search PubMed and Europe PMC for biomedical literature by boolean query, date range, study design, or open-access status. Retrieve citable record summaries with handles for verifying quotes and references.

Instructions

Search PubMed and Europe PMC (including preprints). Returns record summaries; each citable hit has its title passage's handle.

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": {
      "query": "<query>"
    },
    "name": "search_literature"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesBoolean terms. PubMed field tags such as [tiab] search PubMed only; Europe PMC is then skipped and reported as degraded.
cursorNo
date_toNoYYYY or YYYY-MM-DD
sourcesNoDefault: both. Duplicates are merged.
date_fromNoYYYY or YYYY-MM-DD
study_designsNoFrom MEDLINE publication types
open_access_onlyNo
exclude_retractedNo
peer_reviewed_onlyNo

Output Schema

NameRequiredDescriptionDefault
hitsYes
totalYesLargest single-source match count (sources overlap)
totalsNoMatch count per source
next_cursorNo
source_statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds meaningful return behavior beyond that: record summaries and the fact that each citable hit carries its title passage's handle, which helps downstream chaining to resolve_handles or fetch_passages. It omits deduplication, degradation, and rate-limit behavior, hence not 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?

Two compact sentences with the verb and scope front-loaded; nothing is wasted. The phrase 'title passage's handle' is somewhat jargon-heavy and could be clearer, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter federated search tool with half its schema undocumented, the description is too thin: no filtering guidance, no pagination notes, no explanation of degraded-source behavior or how the returned handles are meant to be used. An output schema and read-only annotations exist, but they do not cover the parameter-level gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50% across 10 parameters, so the description must compensate, and it largely does not. It implies both sources are searched by default and references biomedical text sources, but says nothing about limit, cursors, date bounds, study_designs, open_access_only, exclude_retracted, or peer_reviewed_only.

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 resources ('PubMed and Europe PMC, including preprints'), clearly distinguishing this from siblings like search_trials and search_drug_labels. An agent can immediately tell what domain this tool covers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, nor any mention of alternatives such as search_trials or fetch_passages for retrieval. The only routing-like detail ('PubMed field tags such as [tiab]... Europe PMC is then skipped') lives in the schema, not the description.

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