Skip to main content
Glama
Sign In
eprintdl

eprintdl

by Jiangjiang-jiang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Search local eprint library

eprint_search

Search local eprint metadata by keyword, author, abstract, or category to confirm paper IDs before downloading. Returns file paths for already-downloaded entries.

Instructions

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "eprint_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo结束年份（含）
fromNo起始年份（含）
limitNo最多返回多少条（默认 20）
orderNo排序
yearsNo归档年份，如 ["2024"] 或 ["2020-2024"]
keywordNo关键词，匹配标题/作者/摘要/分类
categoryNo分类，如 "Foundations"
downloaded_onlyNo只返回已下载且文件存在的条目

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does add genuine behavioral context — that file_path on downloaded entries is a directly readable local absolute path, and that a missing year requires a separate harvest step — but it says nothing about empty-result behavior, permission/auth needs, or result ordering defaults beyond the schema.

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?

Three short clauses with the core purpose front-loaded, then the download workflow, then the harvest prerequisite. No redundant restatement of the name or title; every clause carries content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter search tool with no output schema and no annotations, the description covers purpose and the two key workflow links (pre-download confirmation, harvest for missing years). It leaves gaps around how the overlapping year filters combine, default paging behavior, and what an empty search yields.

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 every one of the 8 parameters is already documented in the schema. The description only restates that keyword matches title/author/abstract/category, adding no syntax, format, or interaction detail (e.g. how years relates to from/to), so baseline 3 applies.

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?

States a specific verb and resource (检索论文 in 本地 eprint 元数据库) and enumerates the matchable fields (标题/作者/摘要/分类), which maps directly to the keyword parameter. It does not explicitly distinguish itself from eprint_status or eprint_verify, but the download-related note implies a search-vs-fetch split.

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?

Gives concrete when-to-use guidance: call it before downloading to confirm the 编号, and call harvest first when the library lacks the requested year. These are real workflow preconditions rather than generic filler, though 'harvest' is not among the listed sibling tools, leaving the agent unsure how to obtain that capability.

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