Skip to main content
Glama
fangfuzha

article-mcp

by fangfuzha

文献全文

get_article_details
Read-only

Retrieve full text of articles by PMCID. Supports batch mode, section extraction, and multiple output formats.

Instructions

获取文献全文工具。

前置条件:需要 PMCID 标识符

  • 如果您有 PMCID(如 PMC1234567),直接使用此工具

  • 如果您只有关键词或标题,请先使用"文献搜索"工具查找并获取 PMCID

主要参数:

  • pmcid: PMCID 标识符(必填):单个或列表[PMC1234567, PMC2345678, ...] 批量模式最多支持20个 PMCID

  • sections: 全文章节控制(可选,默认None获取全部章节) None → 获取全部章节(全文) ["conclusion", "discussion"] → 只获取指定章节

  • format: 全文格式(可选,默认"markdown") "markdown" → Markdown格式(推荐,适合AI处理) "xml" → 原始XML格式 "text" → 纯文本格式

数据源:Europe PMC + PMC 全文数据库 返回数据包含标题、作者、摘要、期刊、发表日期和全文内容

全文功能:

  • 按需获取指定格式(默认Markdown)

  • 支持按章节提取(如方法、讨论、结论等)

  • 优化性能,只转换请求的格式

批量返回结构: { "total": 10, # 总请求数 "successful": 8, # 成功获取数 "failed": 2, # 失败数 "articles": [...], # 成功的文章列表(含全文) "fulltext_stats": { # 全文统计 "has_pmcid": 8, # 有 PMCID 数量 "fulltext_fetched": 8 # 成功获取全文数量 } }

支持的章节名称:

  • methods(方法): methods, methodology, materials and methods

  • introduction(引言): introduction, intro, background

  • results(结果): results, findings

  • discussion(讨论): discussion

  • conclusion(结论): conclusion, conclusions

  • abstract(摘要): abstract, summary

  • references(参考文献): references, bibliography

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pmcidYes
sectionsNo
formatNomarkdown
Behavior5/5

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

The description extensively covers behavioral aspects: data source (Europe PMC + PMC), return fields, batch structure with stats, format conversion, and section extraction. Annotations indicate readOnlyHint=true, and the description confirms read-only behavior, with no contradictions.

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 well-structured with clear sections (prerequisites, parameters, data source, return structure, supported sections) and front-loaded purpose. Though verbose, every part serves a purpose; a slight reduction in redundancy could improve conciseness.

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?

Given no output schema and limited schema descriptions, the description provides complete context: prerequisites, parameter semantics, return structure example, supported sections, and batch statistics. It also references the sibling search_literature tool for alternative scenarios.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by explaining each parameter in detail: pmcid (required, can be list, max 20), sections (acceptable values and mapping), format (options with recommendations). It adds meaning well beyond the schema.

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 it is a tool for retrieving full text of literature using PMCID. It distinguishes itself from sibling tools by specifying that if only keywords or title are available, the search_literature tool should be used first.

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

Usage Guidelines5/5

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

The description explicitly provides usage guidance: use when you have a PMCID, otherwise use the search_literature tool. It also details batch mode limits and parameter behavior (e.g., sections defaulting to None for full text).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fangfuzha/article-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server