Skip to main content
Glama

fetch_paper

Fetch a paper by DOI, URL, or title and return its structured article, markdown, and metadata with provenance, quality, and token estimates. Enables AI agents to read beyond abstracts.

Instructions

Fetch one paper as structured article, Markdown, and/or metadata with provenance, quality, trace, and token estimates. Defaults are modes=article+markdown, provider-default assets, metadata-only fallback enabled, include_refs=null, max_tokens=full_text, prefer_cache=false, no_download=false, artifact_mode=markdown-assets, and save_markdown=false. The call may access remote services and write provider artifacts, assets, and an MCP cache sidecar. no_download=true suppresses those writes; save_markdown=true is an explicit separate write and returns a path instead of inline full text. artifact_mode=none suppresses provider artifacts but retains MCP cache semantics. asset_profile=none|body|all controls local assets; body/all may return bounded ImageContent. Use prefer_cache=true only with matching request semantics. Current provider/source/runtime/asset-default facts are at resource://paper-fetch/provider-catalog. Access controls and manual-auth boundaries are never bypassed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modesNo
queryYes
strategyNo
max_tokensNofull_text
no_downloadNo
download_dirNo
include_refsNo
prefer_cacheNo
artifact_modeNomarkdown-assets
save_markdownNo
markdown_filenameNo
markdown_output_dirNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
doiNo
codeNo
routeNo
stageNo
traceNo
reasonNo
sourceNo
statusNo
articleNo
detailsNo
qualityNo
markdownNo
metadataNo
providerNo
warningsNo
retryableNo
candidatesNo
http_statusNo
missing_envNo
content_kindNo
has_abstractNo
has_fulltextNo
source_trailNo
error_categoryNo
schema_versionNo
token_estimateNo
retry_after_secondsNo
saved_markdown_pathNo
token_estimate_breakdownNo
Behavior4/5

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

Beyond the annotations, the description discloses that the tool may access remote services and write provider artifacts, MCP cache sidecar, and the effects of no_download and save_markdown. No contradiction with annotations (readOnlyHint=false, openWorldHint=true).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense and long, listing many defaults and behaviors. It is front-loaded with the core purpose but could be more concise. The structure is adequate but not exemplary.

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 complex tool with 12 parameters, nested objects, and side effects, the description covers core defaults, caching, asset profiles, and writes. An output schema exists, so return values need not be detailed. The resource reference for provider catalog adds completeness.

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?

With 0% schema description coverage, the description explains many default values and behaviors for parameters like modes, artifact_mode, no_download, etc. However, some parameters like download_dir, markdown_filename, and strategy subfields are not explained, leaving gaps.

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 action 'fetch one paper' and lists the output formats (article, markdown, metadata), distinguishing it from batch or caching tools. However, it does not explicitly differentiate from sibling tools like resolve_paper or browser_preflight.

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 provides some usage guidance, such as when to use prefer_cache and that access controls are never bypassed, but lacks explicit when-to-use vs. alternatives or when-not-to-use conditions.

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/Dictation354/paper-fetch-skill'

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