Skip to main content
Glama
Dianel555

Paper Search MCP

by Dianel555

search_iacr

Search the IACR ePrint Archive for cryptography papers using keywords to find relevant research publications.

Instructions

Search IACR ePrint Archive for cryptography papers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query string
maxResultsNoMaximum number of results to return
fetchDetailsNoFetch detailed information for each paper (slower)

Implementation Reference

  • MCP tool handler case for 'search_iacr': parses arguments, invokes the IACR searcher, and returns formatted JSON response.
    case 'search_iacr': {
      const { query, maxResults, fetchDetails } = args;
      const results = await searchers.iacr.search(query, { maxResults, fetchDetails });
    
      return jsonTextResponse(
        `Found ${results.length} IACR ePrint papers.\n\n${JSON.stringify(
          results.map((paper: Paper) => PaperFactory.toDict(paper)),
          null,
          2
        )}`
      );
    }
  • Zod schema defining input validation for search_iacr tool: query (required), maxResults, fetchDetails.
    export const SearchIACRSchema = z
      .object({
        query: z.string().min(1),
        maxResults: z.number().int().min(1).max(50).optional().default(10),
        fetchDetails: z.boolean().optional()
      })
      .strip();
  • Tool registration defining name, description, and JSON schema for the search_iacr MCP tool.
    {
      name: 'search_iacr',
      description: 'Search IACR ePrint Archive for cryptography papers',
      inputSchema: {
        type: 'object',
        properties: {
          query: { type: 'string', description: 'Search query string' },
          maxResults: {
            type: 'number',
            minimum: 1,
            maximum: 50,
            description: 'Maximum number of results to return'
          },
          fetchDetails: {
            type: 'boolean',
            description: 'Fetch detailed information for each paper (slower)'
          }
        },
        required: ['query']
      }
    },
  • Core implementation of the IACR ePrint search: sends HTTP GET to search endpoint, handles response, parses results via parseSearchResponse (which uses Cheerio), supports fetching details.
    async search(query: string, options: IACRSearchOptions = {}): Promise<Paper[]> {
      try {
        const params = {
          q: query
        };
    
        logDebug(`IACR API Request: GET ${this.searchUrl}`);
        logDebug('IACR Request params:', params);
    
        const response = await axios.get(this.searchUrl, {
          params,
          timeout: TIMEOUTS.DEFAULT,
          headers: {
            'User-Agent': this.getRandomUserAgent(),
            'Accept': 'text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8',
            'Accept-Language': 'en-US,en;q=0.9'
          }
        });
        
        logDebug(`IACR API Response: ${response.status} ${response.statusText}`);
        
        const papers = await this.parseSearchResponse(response.data, options);
        logDebug(`IACR Parsed ${papers.length} papers`);
        
        return papers.slice(0, options.maxResults || 10);
      } catch (error: any) {
        logDebug('IACR Search Error:', error.message);
        this.handleHttpError(error, 'search');
      }
    }
  • Initialization of the IACRSearcher instance and assignment to the global searchers.iacr object used by handlers.
      const iacrSearcher = new IACRSearcher();
      const googleScholarSearcher = new GoogleScholarSearcher();
      const sciHubSearcher = new SciHubSearcher();
      const scienceDirectSearcher = new ScienceDirectSearcher(process.env.ELSEVIER_API_KEY);
      const springerSearcher = new SpringerSearcher(
        process.env.SPRINGER_API_KEY,
        process.env.SPRINGER_OPENACCESS_API_KEY
      );
      const wileySearcher = new WileySearcher(process.env.WILEY_TDM_TOKEN);
      const scopusSearcher = new ScopusSearcher(process.env.ELSEVIER_API_KEY);
      const crossrefSearcher = new CrossrefSearcher(process.env.CROSSREF_MAILTO);
    
      searchers = {
        arxiv: arxivSearcher,
        webofscience: wosSearcher,
        pubmed: pubmedSearcher,
        wos: wosSearcher,
        biorxiv: biorxivSearcher,
        medrxiv: medrxivSearcher,
        semantic: semanticSearcher,
        iacr: iacrSearcher,
        googlescholar: googleScholarSearcher,
        scholar: googleScholarSearcher,
        scihub: sciHubSearcher,
        sciencedirect: scienceDirectSearcher,
        springer: springerSearcher,
        wiley: wileySearcher,
        scopus: scopusSearcher,
        crossref: crossrefSearcher
      };
    
      logDebug('Searchers initialized successfully');
      return searchers;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'Search' but doesn't describe what the search returns (e.g., paper titles, abstracts, metadata), performance characteristics (e.g., speed implications of fetchDetails), error conditions, or authentication requirements. The phrase 'slower' in the schema hints at performance but isn't elaborated in the description.

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 a single, efficient sentence that directly states the tool's purpose without any wasted words. It's front-loaded with the core action and target, making it easy to parse quickly.

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?

For a search tool with 3 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the search returns (e.g., list of papers with basic info), how results are formatted, or any limitations (e.g., date ranges, sorting options). The lack of output schema means the description should compensate by detailing return values, which it doesn't.

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 the schema already documents all three parameters (query, maxResults, fetchDetails) with their types and constraints. The description adds no additional parameter semantics beyond what's in the schema, maintaining the baseline score of 3 for adequate coverage through structured data alone.

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?

The description clearly states the verb ('Search') and resource ('IACR ePrint Archive for cryptography papers'), making the purpose immediately understandable. It distinguishes from general search tools by specifying the IACR ePrint Archive, though it doesn't explicitly differentiate from sibling tools like search_arxiv that also search academic repositories.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With many sibling search tools (e.g., search_arxiv, search_pubmed, search_google_scholar), there's no indication that this is specifically for cryptography papers from IACR, nor any context about when it might be preferred over other search options.

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/Dianel555/paper-search-mcp-nodejs'

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