Skip to main content
Glama
Sign In
eprintdl

eprintdl

by Jiangjiang-jiang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Download eprint papers

eprint_download

Downloads original IACR Cryptology ePrint Archive PDFs by archive ID to local storage and returns the absolute file path, using a real Chrome window to pass Cloudflare checks.

Instructions

按归档编号下载 eprint 论文的原始 PDF 到本地，返回绝对路径。单篇约 0.5 到 2 秒；首次或凭据失效时需过一次 Cloudflare 质询（约 2 到 8 秒）。会启动一个真实 Chrome 窗口（PDF 路径用 HTTP 客户端会 403，这是预期行为）。已存在的文件会被复用（status=reused），因此可安全重复调用。

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": {
      "paper_ids": "<paper_ids>"
    },
    "name": "eprint_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
paper_idsYes归档编号列表，如 ["2024/1000", "2023/1234"]
lock_timeoutNo等待其它下载任务的最长秒数（默认 300）
no_title_fetchNo缺元数据时不抓单篇页面（文件名只剩编号）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses latency ranges, a first-call Cloudflare challenge cost, that a real Chrome window opens, that an HTTP client will get 403 by design, and that existing files are reused with status=reused. An agent knows exactly what side effects and failures to expect.

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

Conciseness5/5

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

Four dense sentences, zero filler, with the core action and return value front-loaded before the timing/Chrome/idempotency caveats. Every sentence carries information the agent needs.

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?

No output schema exists, yet the description still reports the return shape (absolute path, status=reused). Combined with the timing, authentication-challenge, and idempotency notes, nothing an agent needs to call this correctly is missing.

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 description coverage is 100%, so paper_ids, lock_timeout, and no_title_fetch are already documented in the schema. The description mentions the '文件名只剩编号' consequence that maps to no_title_fetch but adds no format or concurrency detail beyond the schema, so 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+resource ('按归档编号下载 eprint 论文的原始 PDF 到本地') plus the return value (绝对路径). This is unmistakably distinct from the sibling set (eprint_search/status/verify), which are lookup/verification tools, not retrievers of raw PDFs.

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?

Provides useful operating context (single-paper timing, when the Cloudflare challenge applies, that repeats are safe because existing files are reused) but never explicitly says when to prefer a sibling or when not to call this. Usage is implied rather than routed.

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

Deploy Server

Other Tools