Skip to main content
Glama
u9401066

pubmed-search-mcp

by u9401066
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

fetch_article_details

Read-onlyIdempotent

Retrieve detailed metadata for PubMed articles using one or more PMIDs. Accepts single, comma-separated, or list inputs to return complete article information.

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) 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
pmidsYes
output_formatNomarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.3
    • changedInput schema / properties / output_format / enum
      Previous value: -[
-  "markdown",
-  "json"
-]New value: +[
+  "markdown",
+  "json",
+  "toon"
+]
  2. 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
  3. 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 provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds meaningful behavioral detail beyond annotations, especially the batch failure semantics: inputs fail as a complete batch when any PMID is invalid. This is genuinely useful and not inferable from schema or annotations.

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 compact, well-organized with 'Args' and 'Returns', and front-loads the core purpose before parameter details. The bulleted pmids format list is efficient. The only minor issue is the slightly ambiguous phrase 'Inputs are string-only' after listing array support, and the 'Returns' line adds little beyond the first sentence.

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?

For a tool with no output schema, the description covers batch input behavior and the main parameter well. But it omits the output_format parameter, does not explain return details or structure, and lacks guidance on when this tool is preferable to sibling tools. These gaps leave the agent with uncertainty about how to use the tool effectively in a larger workflow.

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 does a good job for pmids by listing accepted formats and the string-only constraint. However, it completely ignores output_format, which is surfaced only in the schema. The enum and default are self-explanatory, but the description still misses an opportunity to clarify formats like 'toon'.

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?

The description clearly states a specific verb ('Fetch') and resource ('detailed information for ... PubMed articles'), and signals batch capability with 'one or more'. However, it does not distinguish this tool from sibling retrieval tools like get_fulltext, find_related_articles, or get_article_figures, so it falls short of full sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives, and it does not mention any exclusions or prerequisites. While the accepted pmids formats are documented, the usage context—such as 'use this for article metadata, get_fulltext for full text'—is entirely absent.

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