Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
eprint_searchA

在本地 eprint 元数据库里检索论文(标题/作者/摘要/分类)。下载前先用它确认编号,已下载条目的 file_path 是可直接读取的本地绝对路径。库里没有该年份时先调用 harvest。

eprint_downloadA

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

eprint_statusA

返回本地库与配置状态:记录数、已下载/失败/待下载、各年份进度、磁盘上 PDF 数量与体积。

eprint_verifyB

校验已下载文件是否为完整 PDF(文件头、%%EOF、体积),列出损坏项。

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 4 tools

Disambiguation5/5

Each tool maps to a clearly different stage of the pipeline: metadata lookup (search), fetching PDFs (download), library/config state (status), and file integrity checks (verify). There is no meaningful overlap — an agent can pick the right tool from the name alone, and the descriptions reinforce the boundaries.

Naming Consistency5/5

All four tools share the same `eprint_` prefix followed by a single lowercase verb/noun in snake_case: search, download, status, verify. The pattern is uniform and predictable; the only mild variation is `status` being a noun rather than a verb, which is idiomatic and unambiguous.

Tool Count4/5

Four tools is well-scoped for a focused eprint downloader and each one earns its place without redundancy. However, the surface is thin enough that a missing operation (e.g. harvest/refresh) pushes the set just past the ideal for its scope.

Completeness3/5

Search/download/status/verify cover the core fetch-and-check loop, but `eprint_search` explicitly instructs the agent to call a `harvest` tool that is not exposed, creating a documented dead end when a year is missing from the local DB. Configuration/credential refresh is also only implied via download's Cloudflare note, so the lifecycle is not fully closed.