PubMed Advanced MCP Server

resolve_article_identifier

Detect the type of any article identifier. Return all associated formats, including PMID, PMCID, DOI, and MID.

Instructions

Resolve a single identifier to all available ID formats.

Automatically detects the ID type and returns all available identifiers for the article.

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": {
      "identifier": "<identifier>"
    },
    "name": "resolve_article_identifier"
  }
}

Input Schema

Name	Required	Description	Default
`identifier`	Yes	Any article ID (PMID, PMCID, DOI, or MID)
`auto_detect_type`	No	Auto-detect the ID type

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description must fully explain behavior. It transparently states that the tool auto-detects the ID type and returns all identifiers, but it does not disclose what happens on invalid input, whether auto_detect_type=false changes behavior, or any error handling details.

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 two short sentences, front-loads the core purpose, and contains no filler. Every word adds value.

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?

For a simple identifier resolution tool with an output schema present, the description adequately covers the main functionality. However, it lacks any mention of error handling or limitations, and the presence of the similar 'convert_article_ids' sibling suggests a bit more context would help.

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?

The schema already documents both parameters with descriptions and 100% coverage. The description adds no significant meaning beyond the schema, though it does reinforce the auto-detection behavior tied to auto_detect_type. This matches the baseline for full schema coverage.

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 the tool resolves a single identifier to all available ID formats, using a specific verb and resource. However, it does not explicitly distinguish itself from the similar sibling tool 'convert_article_ids', so it falls short of a 5.

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 usage when you have a single identifier and need all available ID formats, but it provides no context on when to use this tool instead of alternatives like batch_fetch_articles or convert_article_ids, and no exclusions are mentioned.

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

Deploy Server