Search academic papers from IACR ePrint Archive.
Args:
query: Search query string (e.g., 'cryptography', 'secret sharing').
max_results: Maximum number of papers to return (default: 10).
fetch_details: Whether to fetch detailed information for each paper (default: True).
Returns:
List of paper metadata in dictionary format.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| max_results | No | ||
| fetch_details | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It explains the return format and parameters, but does not explicitly state read-only behavior, rate limits, or potential side effects. It is adequate for a simple search tool but not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The docstring is well-structured with Args and Returns sections, every sentence provides useful information, and there is no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity and lack of output schema, the description covers the purpose, parameters, and return format comprehensively. It is complete for an agent to invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, but the description provides detailed meaning for all three parameters, including examples and defaults. This fully compensates for the lack of schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches academic papers from IACR ePrint Archive, with a specific verb and resource. It distinguishes from sibling archive search tools by naming the archive.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The context is clear: this searches IACR ePrint Archive, implying it should be used for IACR papers. However, it lacks explicit mention of alternatives or when not to use it, so it falls short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Multiple tools appear to serve the same purpose, such as search_arxiv and search-arxiv, or papers-search-basic, paper-search-advanced, search_papers, and search. The download/read tools for different sources follow similar patterns, but some return 'not supported' messages, making it unclear which tools are actually functional.
Tool names mix snake_case, kebab-case, and bare verbs without a consistent pattern. For example, about_nanci, analysis-citation-network, download-full-paper-arxiv, fetch, and search_arxiv all coexist, and the same action for different sources alternates conventions (search-arxiv vs search_arxiv).
With 53 tools, the server is heavily over-scoped. Many tools are redundant or near-duplicates, such as six source-specific search tools plus an aggregate search, and the inclusion of both paper and clinical trial tools in one server creates unnecessary bloat.
The server covers a wide range of research workflows, including search, download, read, citations, authors, and clinical trials. However, several tools (crossref/pubmed download/read) are non-functional dead ends, and the redundancy makes it harder to navigate the surface.