Skip to main content
Glama
Sign In
PubMed MCP Server

PubMed MCP Server

by Augmented-Nature
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_article_details

Retrieve comprehensive metadata and abstract for a PubMed article by PMID. Get structured citation details and research summary in one call.

Instructions

Get comprehensive metadata and abstract for a specific article by PMID

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pmid": "<pmid>"
    },
    "name": "get_article_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
pmidYesPubMed ID (e.g., "12345678")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, and the description does not detail behavioral traits such as rate limits, authentication, or the exact scope of 'metadata', which leaves some ambiguity.

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?

The description is a single, well-structured sentence with no wasted words, efficiently conveying the tool's purpose.

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?

Though adequate for a simple tool with one parameter, the description lacks details about what 'comprehensive metadata' includes and the return format, especially given no output schema.

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 coverage is 100% with a clear description for 'pmid'. The description adds no additional meaning beyond the schema, meeting the baseline for a simple parameter.

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 clearly states the verb 'Get' and the resource 'comprehensive metadata and abstract', which distinguishes it from sibling tools like 'get_abstract' that likely return only the abstract.

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 does not explicitly state when to use this tool versus alternatives like 'get_abstract' or 'get_full_text', though the naming provides some implicit guidance.

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