Skip to main content
Glama
Sign In
pubmed-clinical-mcp

pubmed-clinical-mcp

by jxia622
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

fetch_pubmed_articles

Retrieve detailed PubMed metadata including title, abstract, authors, journal, year, DOI, MeSH terms, and publication types by providing PMIDs.

Instructions

Fetch PubMed title, abstract, authors, journal, year, DOI, MeSH, and publication types.

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": {
      "pmids": "<pmids>"
    },
    "name": "fetch_pubmed_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
pmidsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are present, so the description must cover behavioral traits. It only lists fields retrieved and omits important details such as required authentication, handling of invalid PMIDs, or return format.

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 a single, efficient sentence that lists the fetched fields. It is concise but could be improved by front-loading the verb and input specification.

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

Completeness2/5

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

Given the presence of an output schema and siblings, the description is incomplete. It fails to specify that the tool returns metadata only, how many PMIDs can be processed, or the order of results. The missing details hinder effective use.

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

Parameters1/5

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

The parameter 'pmids' has 0% schema description coverage, and the tool description provides no explanation of its purpose, format, or constraints. The agent receives no guidance on what values to supply.

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 specifies the verb 'fetch' and the resource 'PubMed articles' and lists specific fields retrieved. However, it does not explicitly mention that the input is a list of PMIDs, which is important for clarity.

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 is provided on when to use this tool versus siblings like search_pubmed or fetch_pmc_full_text. The description lacks context for tool selection.

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