Skip to main content
Glama
wos-mcp-bridge

wos-mcp-bridge

Resolve Article

resolve_article
Read-onlyIdempotent

Convert a DOI, PMID, or PMCID into metadata, abstracts, and legal open-access links via Europe PMC and OpenAlex, without downloading publisher URLs.

Instructions

Resolve a DOI, PMID or PMCID to metadata, abstract and legal OA links.

Accepts DOI strings/doi.org URLs, PMID digits/PMID:digits, or PMCdigits. Queries Europe PMC and, for a DOI/PMID, OpenAlex. Never downloads publisher URLs. Missing abstracts are null; access.status is open_access, closed or unknown.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_charsNoMaximum returned text characters; metadata is additional.
identifierYesBare DOI, DOI: prefix, https://doi.org/ URL, PMID digits/PMID:digits, or PMCID PMCdigits; arbitrary URLs and WOS: IDs are rejected.

Output Schema

NameRequiredDescriptionDefault
idYes
doiYes
urlYes
pmidYes
yearNo
pmcidYes
titleYes
accessYes
sourceYes
authorsNo
licenseYes
abstractYes
sectionsYes
warningsYes
retrievalYes
license_urlNo
text_budgetYes
bibliographyYesAdditive common metadata; null means the authoritative value is unavailable.
oa_locationsYes
abstract_truncatedNo
abstract_total_charsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the data sources (Europe PMC, and OpenAlex for DOI/PMID), the no-download guarantee, the null-abstract behavior, and the possible access.status values. Missing are any notes on partial-source failure, fallback ordering when OpenAlex and Europe PMC disagree, or rate limits, so it is not exhaustive.

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?

Four short sentences with the core purpose front-loaded and no filler. The identifier-format sentence partly duplicates the regex-backed schema description, which is slight redundancy but also useful at a glance.

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

Completeness5/5

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

An output schema exists, so return values need not be explained, and the description still flags the key return caveats (null abstracts, access.status enum) and the source behavior. For a two-parameter read-only resolver this leaves nothing an agent needs in order to call it correctly.

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%, so the identifier pattern and max_chars semantics are already documented. The description restates the accepted identifier forms but adds nothing about max_chars or the interaction between returned text and metadata, so the baseline 3 applies.

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?

States a specific verb and resource (resolve an identifier to metadata, abstract, and OA links) and names the accepted identifier types, so an agent can tell it apart from lookup tools like get_article or search_literature. The clause 'Never downloads publisher URLs' further separates it from a fetch-style tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for when the tool applies (DOI/PMID/PMCID resolution) and one explicit exclusion (no publisher URL download, no arbitrary URLs or WOS: IDs via the schema). It does not explicitly route the agent to search_literature for discovery or to get_article for full text, but the applicable scope is unambiguous.

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