Skip to main content
Glama
wos-mcp-bridge

wos-mcp-bridge

Get Article

get_article
Read-onlyIdempotent

Retrieves an article's Europe PMC open-access XML as JATS sections with a text budget, preserving headings and IDs; non-OA items return metadata and abstract only.

Instructions

Retrieve available Europe PMC OA XML as JATS sections, with a total text budget.

Returns abstract and sections preserving headings, IDs and parent IDs. include_text=False returns the section directory plus bounded abstract. Metadata-reported XML availability can fail (see warnings). Non-OA articles return available metadata/abstract only. Use get_article_section with section.id and next_offset to read omitted text.

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": "get_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.
include_textNoInclude bounded section text; false returns the section directory and abstract.

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.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the description correctly spends its words elsewhere: the text budget, the meaning of include_text=False, the caveat that metadata-reported XML availability can fail (see warnings), and the degraded result for non-OA articles. These are real behavioral traits not derivable from annotations. It does not cover truncation signaling or how warnings surface, which keeps it off a 5.

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?

Five short sentences, front-loaded with the core action and budget before the caveats and the sibling routing. A stray mid-sentence line break around 'include_text=False' slightly hurts scanning, but there is no filler.

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?

Given three parameters, an output schema, and full annotation coverage, the description covers the essentials: return shape, budget interaction, degraded non-OA path, and the continuation mechanism. It stops short of explaining how truncation or warnings are surfaced in the response, which is the only remaining ambiguity for an agent deciding whether to follow up.

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 baseline is 3. The description frames max_chars as a 'total text budget' and restates the include_text=False behavior, but the schema descriptions already say 'Maximum returned text characters; metadata is additional' and 'false returns the section directory and abstract' — so the added meaning is marginal rather than new.

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 states a specific verb and resource ('Retrieve available Europe PMC OA XML as JATS sections') and scopes it with a text budget, so the agent knows exactly what comes back. It also distinguishes itself from the sibling get_article_section by explaining that one is for reading omitted text.

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?

Routing is explicit for the main fork: set include_text=False for just the directory, and use get_article_section with section.id and next_offset for text that was omitted. The non-OA fallback ('return available metadata/abstract only') is also stated. What is missing is any guidance on when to pick this over resolve_article or fetch.

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