Skip to main content
Glama
flyanima

Open Search MCP

by flyanima

search_iacr

Search the IACR (International Association for Cryptologic Research) database for cryptography research papers using query keywords. Specify the maximum number of results (1-100) to retrieve.

Instructions

Search IACR (International Association for Cryptologic Research) for cryptography papers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query for cryptography research
maxResultsNoMaximum number of results to return

Implementation Reference

  • The search_iacr tool is registered via the registerBioRxivTools() function calling registry.registerTool() with name 'search_iacr'
    export function registerBioRxivTools(registry: ToolRegistry): void {
      // IACR Cryptography Research Tool
      registry.registerTool({
        name: 'search_iacr',
        description: 'Search IACR (International Association for Cryptologic Research) for cryptography papers',
        category: 'academic',
        source: 'IACR',
        inputSchema: {
          type: 'object',
          properties: {
            query: {
              type: 'string',
              description: 'Search query for cryptography research'
            },
            maxResults: {
              type: 'number',
              description: 'Maximum number of results to return',
              default: 20,
              minimum: 1,
              maximum: 100
            }
          },
          required: ['query']
        },
        execute: async (args: ToolInput): Promise<ToolOutput> => {
          try {
            const { query, maxResults = 20 } = args;
    
            // Simulated IACR search results
            const results = Array.from({ length: Math.min(maxResults, 10) }, (_, i) => ({
              title: `Cryptographic Analysis of ${query} - Paper ${i + 1}`,
              authors: [`Dr. Crypto Expert ${i + 1}`, `Prof. Security Researcher ${i + 1}`],
              abstract: `This paper presents a comprehensive analysis of ${query} in the context of modern cryptographic systems...`,
              venue: i % 2 === 0 ? 'CRYPTO' : 'EUROCRYPT',
              year: 2024 - (i % 3),
              url: `https://eprint.iacr.org/2024/${String(i + 1).padStart(3, '0')}`,
              category: 'Cryptography',
              keywords: [query, 'cryptography', 'security', 'algorithms']
            }));
    
            return {
              success: true,
              data: {
                source: 'IACR',
                query,
                results,
                totalResults: results.length
              },
              metadata: {
                searchTime: Date.now(),
                source: 'IACR ePrint Archive'
              }
            };
          } catch (error) {
            return {
              success: false,
              error: `IACR search failed: ${error instanceof Error ? error.message : String(error)}`,
              data: null
            };
          }
        }
      });
  • Input schema for search_iacr: requires 'query' (string) and optional 'maxResults' (number, 1-100, default 20)
    inputSchema: {
      type: 'object',
      properties: {
        query: {
          type: 'string',
          description: 'Search query for cryptography research'
        },
        maxResults: {
          type: 'number',
          description: 'Maximum number of results to return',
          default: 20,
          minimum: 1,
          maximum: 100
        }
      },
      required: ['query']
    },
  • Execute handler for search_iacr: generates simulated IACR ePrint cryptography paper results (up to 10), returns success/error response
    execute: async (args: ToolInput): Promise<ToolOutput> => {
      try {
        const { query, maxResults = 20 } = args;
    
        // Simulated IACR search results
        const results = Array.from({ length: Math.min(maxResults, 10) }, (_, i) => ({
          title: `Cryptographic Analysis of ${query} - Paper ${i + 1}`,
          authors: [`Dr. Crypto Expert ${i + 1}`, `Prof. Security Researcher ${i + 1}`],
          abstract: `This paper presents a comprehensive analysis of ${query} in the context of modern cryptographic systems...`,
          venue: i % 2 === 0 ? 'CRYPTO' : 'EUROCRYPT',
          year: 2024 - (i % 3),
          url: `https://eprint.iacr.org/2024/${String(i + 1).padStart(3, '0')}`,
          category: 'Cryptography',
          keywords: [query, 'cryptography', 'security', 'algorithms']
        }));
    
        return {
          success: true,
          data: {
            source: 'IACR',
            query,
            results,
            totalResults: results.length
          },
          metadata: {
            searchTime: Date.now(),
            source: 'IACR ePrint Archive'
          }
        };
      } catch (error) {
        return {
          success: false,
          error: `IACR search failed: ${error instanceof Error ? error.message : String(error)}`,
          data: null
        };
      }
    }
  • src/index.ts:225-234 (registration)
    registerBioRxivTools is called in registerAllTools() which registers 3 tools including search_iacr
    private async registerAllTools(): Promise<void> {
      this.logger.info('Registering exactly 33 specialized tools...');
    
      // 🎓 Academic Research (7 tools)
      registerAcademicTools(this.toolRegistry);           // 1 tool: search_arxiv
      registerPubMedTools(this.toolRegistry);             // 1 tool: search_pubmed
      registerIEEETools(this.toolRegistry);               // 1 tool: search_ieee
      registerSemanticScholarTools(this.toolRegistry);    // 1 tool: search_semantic_scholar
      registerBioRxivTools(this.toolRegistry);            // 3 tools: search_iacr, search_medrxiv, search_biorxiv
  • Maps 'iacr_search' source to tool name 'search_iacr_paper_search_server' in saturated search manager
    private getToolNameForSource(source: SearchSourceConfig): string {
      // 建立搜索源ID到实际MCP工具名称的完整映射
      const toolMappings: Record<string, string> = {
        // 学术搜索工具 - 使用专门的paper search工具
        'google_scholar': 'search_google_scholar_paper_search_server',
        'pubmed_search': 'search_pubmed_paper_search_server',
        'arxiv_search': 'search_arxiv_paper_search_server',
        'semantic_scholar': 'search_semantic_paper_search_server',
        'biorxiv_search': 'search_biorxiv_paper_search_server',
        'medrxiv_search': 'search_medrxiv_paper_search_server',
        'iacr_search': 'search_iacr_paper_search_server',
Behavior1/5

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

No annotations exist, so the description bears full responsibility for behavioral disclosure. It does not mention whether the tool is read-only, requires authentication, has rate limits, or any other behavioral traits, leaving the agent uninformed about side effects or constraints.

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?

The description is a single concise sentence with no fluff. It is front-loaded with the tool's primary action and target, but the brevity sacrifices useful detail.

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?

Given the tool's simplicity (2 parameters, no output schema), the description is too minimal. It does not explain the search scope, result format, or any edge cases, leaving significant gaps for effective invocation.

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?

The input schema provides descriptions for both parameters (query and maxResults), so schema coverage is 100%. The description adds no extra meaning beyond the schema, which is acceptable but not beneficial. Baseline 3 is appropriate.

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 the specific resource 'IACR for cryptography papers', making the basic purpose understandable. However, it does not differentiate from sibling search tools like search_arxiv or search_semantic_scholar, which also handle academic papers.

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?

No guidance is provided on when to use this tool versus alternatives, nor any context about prerequisites or limitations. The single sentence offers no usage recommendations.

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/flyanima/open-search-mcp'

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