Skip to main content
Glama
u9401066

pubmed-search-mcp

by u9401066
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

fetch_article_details

Read-onlyIdempotent

Retrieve detailed information for one or more PubMed articles from their PMIDs. Supports various input formats and returns comprehensive details.

Instructions

Fetch detailed information for one or more PubMed articles.

Args: pmids: PubMed IDs - accepts multiple formats: - "12345678" (single) - "12345678,87654321" (comma-separated) - "PMID:12345678" (with prefix) - ["12345678", "87654321"] (list) - '["12345678", "87654321"]' (JSON array string) - Newlines, semicolons, pipes, and Chinese separators are also accepted. Inputs are string-only and fail as a complete batch when any PMID is invalid.

Returns: Detailed information for each article.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pmidsYesExplicit PMIDs; last is not supported.
output_formatNomarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.7.7
    • addedInput schema / properties / output_format / anyOf
      Added value: +[
+  {
+    "default": "markdown",
+    "enum": [
+      "markdown",
+      "json",
+      "toon"
+    ],
+    "title": "Output Format",
+    "type": "string"
+  },
+  {
+    "pattern": "^[ \\t\\r\\n]*(?:[mM][aA][rR][kK][dD][oO][wW][nN]|[jJ][sS][oO][nN]|[tT][oO][oO][nN])[ \\t\\r\\n]*$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / output_format / enum
      Removed value: -[
-  "markdown",
-  "json",
-  "toon"
-]
    • removedInput schema / properties / output_format / type
      Removed value: -"string"
    • changedInput schema / properties / pmids / anyOf
      Previous value: -[
-  {
-    "maxLength": 100000,
-    "minLength": 1,
-    "type": "string"
-  },
-  {
-    "items": {
-      "maxLength": 512,
-      "minLength": 1,
-      "type": "string"
-    },
-    "maxItems": 1000,
-    "minItems": 1,
-    "type": "array"
-  }
-]New value: +[
+  {
+    "description": "Complete PMID(s): delimited text, JSON string array, or Markdown list; optional JSON code fence. last only where supported.",
+    "examples": [
+      "33053718,36170657",
+      "[\"33053718\",\"36170657\"]",
+      "- 33053718\n- 36170657"
+    ],
+    "format": "pubmed-pmid-batch",
+    "maxLength": 100000,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "items": {
+      "description": "Complete identifier string; optional identifier prefix, official article URL, or inline backticks. No numbers, foreign hosts, URL queries/fragments or partial identifiers.",
+      "examples": [
+        "33053718",
+        "PMID:33053718",
+        "https://pubmed.ncbi.nlm.nih.gov/33053718/"
+      ],
+      "format": "pubmed-pmid",
+      "maxLength": 512,
+      "minLength": 1,
+      "type": "string",
+      "x-pubmed-input": "pmid"
+    },
+    "maxItems": 1000,
+    "minItems": 1,
+    "type": "array"
+  }
+]
    • addedInput schema / properties / pmids / description
      Added value: +"Explicit PMIDs; last is not supported."
    • addedInput schema / properties / pmids / x-pubmed-input
      Added value: +"pmid_batch"
  2. Changed1 schema field changedv0.7.3
    • changedInput schema / properties / output_format / enum
      Previous value: -[
-  "markdown",
-  "json"
-]New value: +[
+  "markdown",
+  "json",
+  "toon"
+]
  3. Changed3 schema fields changedv0.7.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / pmids / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "integer"
-  }
-]New value: +[
+  {
+    "maxLength": 100000,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "items": {
+      "maxLength": 512,
+      "minLength": 1,
+      "type": "string"
+    },
+    "maxItems": 1000,
+    "minItems": 1,
+    "type": "array"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "fetch_article_detailsOutput",
-  "type": "object"
-}New value: +null
  4. First observedv0.5.16

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description nonetheless adds a real behavioral trait beyond them: inputs are string-only and the whole batch fails if any single PMID is invalid — an all-or-nothing failure mode an agent must plan around.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The Args block is well organized and front-loads the key batch-failure constraint, but the long format enumeration partially duplicates the schema examples, and the 'Returns: Detailed information for each article' line is nearly tautological and adds little.

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?

No output schema exists, yet the return value is described only as 'detailed information for each article', leaving the agent unsure what fields come back. Combined with no usage guidance, the definition is adequate for calling but thin on what to expect and when to choose it.

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?

With schema coverage at 50%, the description compensates well for the pmids parameter, enumerating single, comma-separated, prefixed, list, JSON-array-string forms plus newlines, semicolons, pipes and Chinese separators — more than the schema examples convey. It says nothing about output_format, which the schema's enum/default already covers.

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 and resource: 'Fetch detailed information for one or more PubMed articles.' This is clear enough to distinguish from lookup-style siblings like get_fulltext or get_citation_metrics, though it never explicitly names what it is not versus those tools.

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?

No guidance on when to use this versus alternatives such as get_fulltext (full text), get_citation_metrics (metrics), or get_article_figures. The description assumes the agent already knows it wants article metadata; there are no exclusions or prerequisites.

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

Deploy Server

Other Tools