Skip to main content
Glama

parse_pmcid

Retrieves open-access articles from Europe PMC by PMCID and parses full text and supplements into a structured map, enabling batch assessment without a local file.

Instructions

CONVENIENCE / BATCH entry point: retrieve an open-access article from Europe PMC by PMCID and parse it. Reach for this in the corpus/batch case (no file in hand) or to auto-fetch an open-access paper's supplement; for a single manuscript you were given, use parse_manuscript instead. Fetches JATS main text plus (if available) PMC-hosted supplementary files, merged into one source-tagged SectionMap. supplement_status is 'retrieved' when a supplement was obtained, else 'not_retrieved' (a supplement may still exist on the publisher site; absence of retrieval is not proof of absence). Raises if no open-access full text is available. Returns the same summary as parse_manuscript, including the text hash for assess_manuscript. An APA-style citation is auto-built from the article's JATS metadata and displayed on every rendered checklist; pass citation= to override it (e.g. when the auto-built reference is incomplete).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pmcidYes
citationNo
include_supplementsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNo
n_pagesNo
citationNo
sectionsNo
warningsNo
documentsNo
full_textNo
text_sha256No
manuscript_idNo
extractor_versionNo
supplement_statusNo
flow_diagram_detectedNo
protocol_table_detectedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It covers fetching behavior (JATS plus supplements), supplement_status interpretation, the error condition (raises if no open-access full text), the return relation to parse_manuscript, and the auto-built citation with override. This is rich, concrete context beyond what the schema shows.

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?

Every sentence in this multi-sentence description adds functional information: batch use, alternative, fetch scope, status semantics, error, return, and citation. No filler or repetition; dense but scannable.

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?

Despite no annotations, the description covers selection criteria, behavior, error handling, return type (same summary as parse_manuscript), and an override option. The presence of an output schema covers structural return details, so the description is effectively complete for an agent deciding whether and how to invoke this tool.

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 clarifies pmcid (by PMCID from Europe PMC) and citation (override auto-built reference), but include_supplements is only implicitly covered by the statement that supplements are fetched if available. The description never explicitly names the parameter or explains the effect of setting it false, leaving partial compensation.

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 opens with a clear verb-object pair: 'retrieve an open-access article from Europe PMC by PMCID and parse it.' It also explicitly distinguishes itself from parse_manuscript, so an agent can select between siblings without reading 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 Guidelines5/5

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

States exactly when to choose this tool: 'corpus/batch case (no file in hand)' or 'auto-fetch an open-access paper's supplement' and when not to: 'for a single manuscript you were given, use parse_manuscript instead.' Also ties its output to assess_manuscript via the text hash, strengthening routing.

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