Skip to main content
Glama

fetch_paper

Fetch a paper by DOI, URL, or title to get structured Markdown full text, metadata, and assets, enabling 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
acceptanceNo
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
diagnostic_artifactsNo
token_estimate_breakdownNo
Behavior5/5

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

The description discloses significant behavioral traits beyond annotations: it may access remote services, write provider artifacts/assets/MCP cache sidecar, and clarifies that no_download suppresses writes while save_markdown is a separate write. It also mentions access controls and auth boundaries, adding value beyond the readOnlyHint=false and openWorldHint=true annotations. No contradiction.

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 dense and lengthy but every sentence carries technical value, covering defaults, side effects, and option behaviors. The structure is a compact paragraph with semicolons, which is efficient for a tool with many options, though it could be more scannable with bullet points.

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 12 parameters, nested objects, and an output schema, the description is remarkably complete. It covers defaults, side effects, cache semantics, asset behavior, a resource link for provider catalog, and access control guarantees. The output schema exists, so return values need no explanation. The description rounds out the tool's operational context fully.

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

Parameters4/5

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

With schema coverage at 0%, the description compensates by explaining key parameters: modes, include_refs, max_tokens, prefer_cache, no_download, artifact_mode, save_markdown, and asset_profile. It clarifies semantics like save_markdown returning a path instead of inline text and asset_profile controlling local assets. Some parameters (e.g., download_dir, markdown_filename) remain undocumented, but the description covers the most complex ones.

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 a specific action ('Fetch one paper') and the resource (paper), while enumerating output formats (structured article, Markdown, metadata). This distinguishes it from siblings like batch_fetch or resolve_paper, making the purpose unambiguous.

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?

The description offers clear contextual guidance on defaults and option semantics (e.g., 'no_download=true suppresses writes', 'Use prefer_cache=true only with matching request semantics'). It does not explicitly name sibling tools for exclusion, but the usage context is sufficiently clear for an agent to decide when to invoke this tool.

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