Skip to main content
Glama
h-lu

Paper Search MCP Server

by h-lu

search_iacr

Search the IACR ePrint Archive for free cryptography papers on encryption, blockchain, zero-knowledge proofs, and security protocols. Returns paper IDs, titles, authors, abstracts, and PDF links for further download or reading.

Instructions

Search cryptography papers on IACR ePrint Archive.

USE THIS TOOL WHEN:
- Searching for cryptography or security research
- You need papers on encryption, blockchain, zero-knowledge proofs
- Looking for security protocols, hash functions, signatures

DOMAIN: Cryptography ONLY - encryption, signatures, protocols,
blockchain, secure computation, zero-knowledge, hash functions.

All papers are FREE and open access with PDF download.

WORKFLOW:
1. search_iacr(query) -> get paper_id (e.g., '2024/123')
2. download_iacr(paper_id) or read_iacr_paper(paper_id)

Args:
    query: Crypto terms (e.g., 'zero knowledge', 'homomorphic encryption').
    max_results: Number of results (default: 10).
    fetch_details: Get full metadata per paper (default: True).

Returns:
    List of paper dicts with: paper_id, title, authors, abstract,
    published_date, pdf_url.

Example:
    search_iacr("post-quantum cryptography", max_results=5)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
max_resultsNo
fetch_detailsNo
Behavior4/5

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

With no annotations, the description discloses that papers are free, open access, and outlines the workflow (search then download/read). It does not mention rate limits or authentication, but it is reasonably transparent for a search tool.

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?

The description is well-structured with sections for purpose, usage, domain, workflow, args, returns, and example. Every sentence adds value, and the critical information is front-loaded.

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 no output schema, the description details the return format (list of dicts with fields). It also connects to sibling tools via workflow, making the tool's role in a larger process clear.

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

Parameters5/5

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

Despite 0% schema description coverage, the description explains each parameter (query, max_results, fetch_details) with examples and defaults, fully compensating for the lacking schema metadata.

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 tool searches cryptography papers on IACR ePrint Archive, with a specific verb and resource. It distinguishes from sibling tools by explicitly limiting domain to cryptography.

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 'USE THIS TOOL WHEN' section explicitly lists when to use, and the 'DOMAIN: Cryptography ONLY' provides a clear exclusion. However, it does not explicitly mention alternative sibling tools like search_semantic or search_arxiv for non-cryptography needs.

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/h-lu/paper-find-mcp'

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