Skip to main content
Glama
heewon-chung

eprint-mcp-server

by heewon-chung

search_papers

Search the IACR Cryptology ePrint Archive for research papers by title, abstract, or keywords. Filter results by author, category, or date range.

Instructions

Search for papers in the IACR ePrint Archive

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query for title, abstract, or keywords
authorNoFilter by author name (optional)
dateToNoEnd date filter in YYYY-MM-DD format (optional)
sortByNoSort results by relevance, date, or title (default: relevance)relevance
categoryNoFilter by category (optional)
dateFromNoStart date filter in YYYY-MM-DD format (optional)
maxResultsNoMaximum number of results to return (default: 20)
Behavior2/5

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

No annotations are provided, so the description must convey behavior. It fails to mention pagination, rate limits, result format (metadata only?), or matching scope, leaving significant gaps.

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?

A single sentence with no wasted words, but it could be expanded with minimal cost to convey key details.

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

Completeness2/5

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

No output schema is provided, and the description does not explain the return format, limiting an agent's understanding of what to expect.

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 coverage is 100%, so the description adds no parameter meaning beyond the schema; baseline score is appropriate.

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 the verb 'Search' and the resource 'papers in the IACR ePrint Archive', which distinguishes it from sibling tools like download_paper and get_recent_papers.

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?

No explicit guidance on when to use this tool versus alternatives like get_recent_papers; usage is implied but not clarified.

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/heewon-chung/eprint-mcp-server'

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