Skip to main content
Glama
u9401066

pubmed-search-mcp

by u9401066
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_article_figures

Read-onlyIdempotent

Extract figure metadata, captions, image URLs, and PDF links from PMC Open Access articles. Retrieve all figures, sub-figures, and image-based tables using a PMID or PMCID.

Instructions

Get structured figure metadata (label, caption, image URL) and PDF links from a PMC Open Access article.

Returns all figures with their captions and direct image URLs, plus PDF download links for the complete article.

source is a discriminated identifier object, so the schema itself requires exactly one explicit PMID or PMCID.

Args: source: {"kind":"pmcid","value":"PMC12086443"} or {"kind":"pmid","value":"40384072"}. include_subfigures: Parse sub-figures (e.g., Figure 3A, 3B) as separate entries. include_tables: Also extract tables rendered as images.

Returns: Structured figure data with image URLs, captions, and PDF links.

Example: get_article_figures(source={"kind":"pmcid","value":"PMC12086443"})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYes
output_formatNomarkdown
include_tablesNo
include_subfiguresNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.7.2
    • addedInput schema / $defs
      Added value: +{
+  "PMCIDSource": {
+    "additionalProperties": false,
+    "description": "An explicit PubMed Central identifier.",
+    "properties": {
+      "kind": {
+        "const": "pmcid",
+        "title": "Kind",
+        "type": "string"
+      },
+      "value": {
+        "maxLength": 23,
+        "pattern": "^PMC[1-9][0-9]{0,19}$",
+        "title": "Value",
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "value"
+    ],
+    "title": "PMCIDSource",
+    "type": "object"
+  },
+  "PMIDSource": {
+    "additionalProperties": false,
+    "description": "An explicit PubMed identifier.",
+    "properties": {
+      "kind": {
+        "const": "pmid",
+        "title": "Kind",
+        "type": "string"
+      },
+      "value": {
+        "maxLength": 20,
+        "pattern": "^[1-9][0-9]{0,19}$",
+        "title": "Value",
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "value"
+    ],
+    "title": "PMIDSource",
+    "type": "object"
+  }
+}
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / identifier
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Identifier"
-}
    • removedInput schema / properties / pmcid
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Pmcid"
-}
    • removedInput schema / properties / pmid
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Pmid"
-}
    • addedInput schema / properties / source
      Added value: +{
+  "discriminator": {
+    "mapping": {
+      "pmcid": "#/$defs/PMCIDSource",
+      "pmid": "#/$defs/PMIDSource"
+    },
+    "propertyName": "kind"
+  },
+  "oneOf": [
+    {
+      "$ref": "#/$defs/PMIDSource"
+    },
+    {
+      "$ref": "#/$defs/PMCIDSource"
+    }
+  ],
+  "title": "Source"
+}
    • addedInput schema / required
      Added value: +[
+  "source"
+]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_article_figuresOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.5.16

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds meaningful context beyond annotations: it restricts to PMC Open Access articles, explains that PDF links are returned, and clarifies the effects of include_subfigures and include_tables. It does not discuss authentication or rate limits, but these are likely unnecessary for a read-only open API.

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 structured with Args, Returns, and Example sections and front-loads the core purpose. However, the return information is repeated across the opening paragraph and the Returns section, which is mildly redundant.

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

Completeness4/5

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

Given four parameters (one required), no output schema, and annotations that cover safety, the description provides example usage, return content, and parameter guidance, making it largely complete. The missing semantics for output_format and the absence of error or empty-result behavior are minor gaps.

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 0% schema description coverage, the description compensates well for three of four parameters: source is explained with example JSON objects and a note about the discriminated union, and include_subfigures and include_tables are described in functional terms. The output_format parameter is not mentioned at all, leaving a notable gap in parameter semantics.

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 states a specific verb and resource ('Get structured figure metadata... and PDF links') and scopes it to a PMC Open Access article, clearly differentiating it from tools that fetch full text, references, or general image searches. The inclusion of output fields (label, caption, image URL, PDF links) makes the purpose unmistakable.

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 description implies use when figures from a PMC Open Access article are needed, but it does not explicitly state when to use this tool versus alternatives like fetch_article_details, get_fulltext, or search_biomedical_images. No conditions or exclusions are provided.

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