Skip to main content
Glama

parse_pmcid

Fetch and parse an open-access article from Europe PMC by its PMCID, merging main text and supplements into one source-tagged bundle. Use when you have a PMCID but no local manuscript file.

Instructions

CONVENIENCE entry point: retrieve an open-access article from Europe PMC by PMCID and parse it, main text plus PMC-hosted supplements, merged into one source-tagged bundle. Use it when you have no file in hand, or to auto-fetch an open-access paper's supplement; for a manuscript you were given, use parse_document.

supplement_status is 'retrieved' when a supplement was obtained, else 'not_retrieved' — a supplement may still exist on the publisher site, so absence of retrieval is never proof of absence. Raises if no open-access full text is available. An APA-style citation is built from the article's JATS metadata; pass citation= to override it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pmcidYes
citationNo
include_supplementsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNo
n_pagesNo
citationNo
sectionsNo
warningsNo
documentsNo
full_textNo
next_stepNo
cue_surveyNo
text_sha256No
manuscript_idNo
extractor_versionNo
supplement_statusNo
Behavior5/5

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

With no annotations, the description carries the burden and does so well: it discloses the raising behavior when no open-access full text exists, the meaning of supplement_status, and that absence of retrieval does not prove absence of a supplement. These are non-obvious and important behavioral details.

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 description is dense but each sentence adds value: purpose, usage alternative, edge-case behavior, and citation override. It is slightly longer than necessary, but well-structured and front-loaded with the most important information.

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

Completeness5/5

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

The tool has an output schema, so return structure need not be repeated. The description provides error behavior, supplement semantics, citation override, and sibling-tool differentiation, making it complete for an agent to select and invoke correctly.

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 0%, so the description must compensate. It explicitly explains the citation override parameter and implies include_supplements behavior through the supplement-fetching context, but it never names or fully clarifies include_supplements as a boolean toggle. Partial compensation with a clear gap.

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 retrieves an open-access article from Europe PMC by PMCID and parses it into a source-tagged bundle. It immediately distinguishes itself from parse_document, making it specific and actionable.

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

Usage Guidelines5/5

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

Explicitly says to use this when no file is in hand or to auto-fetch an open-access supplement, and directs users with a manuscript to parse_document instead. This is clear when-to-use and alternative guidance.

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/Black-Swan-Causal-Labs/robins-i-mcp'

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