pubmed-mcp-server

Overview Schema Source Related Servers Score Discussions Admin

Pubmed Europepmc Fetch

pubmed_europepmc_fetch

Read-only

Fetch complete Europe PMC records with full, untruncated abstracts using source and epmcId, including preprints, patents, and Agricola records without PMID or DOI.

Instructions

Fetch complete Europe PMC records — including the full, untruncated abstract — for records addressed by source plus epmcId. Pairs with pubmed_europepmc_search, which returns bounded abstractSnippet values and flags cut ones with abstractTruncated: true; pass those hits' source and epmcId here to read the whole abstract. This is the retrieval path for preprint (PPR), patent (PAT), and Agricola (AGR) records, which frequently carry no PMID and no DOI, so pubmed_fetch_articles and pubmed_fetch_fulltext cannot address them. Up to 25 records per call.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`records`	Yes	Records to retrieve, each addressed by the `source` and `epmcId` of a `pubmed_europepmc_search` hit. The whole batch resolves in one Europe PMC request.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Guidance when one or more requested records could not be resolved. Absent when every record came back.
`records`	No	Resolved records, in the order Europe PMC returned them
`notFound`	No	Requested `source` + `epmcId` pairs Europe PMC returned no record for

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.10.8Sep 9, 2026

changedOutput schema / properties / records / items / properties / authors / description

Previous value: -"Formatted author string"New value: +"Formatted author string as display-ready plain text — JATS/HTML markup stripped and HTML entities decoded."

changedOutput schema / properties / records / items / properties / journal / description

Previous value: -"Journal title"New value: +"Journal title as display-ready plain text — JATS/HTML markup stripped and HTML entities decoded."

changedOutput schema / properties / records / items / properties / title / description

Previous value: -"Record title"New value: +"Record title as display-ready plain text — JATS/HTML markup stripped and HTML entities decoded."

Changed6 schema fields changedv2.10.4Aug 28, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "records"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `europepmc_unreachable`: Europe PMC was unreachable after all retry attempts. `europepmc_invalid_response`: Europe PMC returned a body that could not be parsed (invalid JSON or XML). `europepmc_invalid_input`: Europe PMC rejected the request input (empty query, unknown sort field, malformed parameter). `europepmc_disabled`: Europe PMC service is disabled via EUROPEPMC_ENABLED=false. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "europepmc_unreachable",
+            "europepmc_invalid_response",
+            "europepmc_invalid_input",
+            "europepmc_disabled"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required
```
Removed value: -[
-  "records"
-]
```

Addedv2.10.2Jul 30, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses that this tool returns untruncated abstracts, processes up to 25 records per call, and resolves the whole batch in one Europe PMC request. It also explains the MED-versus-PMC behavior in the schema and how truncated search snippets map to this tool, giving agents concrete behavioral expectations.

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 earns its place: core purpose, truncation relationship, alternative tool exclusion, and batch limit. The key behavior is front-loaded, and the description is informative without redundancy.

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?

With an output schema present, return-value documentation is unnecessary, and the description covers the essential operational context: what to pass, when to use it, why it exists versus siblings, and the batch limit. There are no obvious gaps an agent would face when selecting or invoking this tool.

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

Parameters4/5

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

Schema coverage is 100% and the schema already documents `source` and `epmcId` with enum values, patterns, and copy-from-search-hit guidance. The description adds workflow-level semantic value by telling the agent to pass the search hit's `source` and `epmcId`, and reinforces the batch limit, but it does not substantially redefine the parameter meanings.

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 specific verb and resource: 'Fetch complete Europe PMC records — including the full, untruncated abstract — for records addressed by `source` plus `epmcId`.' It clearly distinguishes itself from `pubmed_europepmc_search` and from `pubmed_fetch_articles`/`pubmed_fetch_fulltext` by naming exactly what makes this tool the right retrieval path.

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?

The description gives explicit when-to-use guidance: pair it with `pubmed_europepmc_search`, pass the hit's `source` and `epmcId`, and use it for PPR/PAT/AGR records that lack PMID/DOI and therefore cannot be handled by sibling fetch tools. It also states the 25-record per-call limit, making the usage boundary unambiguous.

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

Install Server