Skip to main content
Glama

fetch_passages

Read-only

Retrieve passages from PubMed, clinical trial, and other biomedical records with citable handles and retraction status, so quotes and citations in an answer can be audited for authenticity.

Instructions

Fetch records (pmid:, pmcid:, ppr:, nct:, setid:) and their passages. Every passage carries a citable handle; articles with a DOI get Crossref's retraction status.

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": {
      "record_ids": "<record_ids>"
    },
    "name": "fetch_passages"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
sectionsNoPath prefixes to keep, e.g. ['abstract']
full_textNoAdd open-access full text (pmcid: records, body.* passages)
record_idsYese.g. pmid:30831578, nct:NCT04368728 or setid:<SPL set ID>
max_passagesNo
include_entitiesNoPubTator3 entities on PubMed passages

Output Schema

NameRequiredDescriptionDefault
recordsYes
not_foundNo
next_cursorNo
unavailableNoRequested records whose source did not answer
source_statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/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 description's job is to add substance — and it does: every passage carries a citable handle, and DOI-bearing articles surface Crossref retraction status. It omits batching limits (max 20 IDs), pagination via cursor, and cost/latency behavior for open-access full text.

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 sentences, front-loaded with the core action and scope, with no filler. The parenthetical ID list is dense but earns its place by defining accepted inputs.

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

Completeness3/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 not required, and the description covers identity syntax and the retraction/handle signals. For a 6-parameter tool it still leaves pagination, section filtering, and full-text toggling to the schema alone, which is adequate but not complete.

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 coverage is 67%, so the baseline is 3. The description reinforces the record_ids namespace syntax but says nothing about sections path prefixes, full_text, include_entities, max_passages, or cursor, leaving roughly a third of the parameters documented only by their schema text.

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 (fetch) and resource (records plus their passages), and enumerates the accepted ID namespaces (pmid:, pmcid:, ppr:, nct:, setid:), which makes the tool's scope concrete. It does not explicitly contrast itself with search_literature or resolve_handles, so sibling differentiation is left implicit.

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 ID-prefix list implies this is the retrieval path when you already hold identifiers, which is useful implied guidance. However, there is no explicit when-to-use/when-not statement and no pointer to search_literature for discovery or resolve_handles for ID resolution.

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