Skip to main content
Glama
flyanima

Open Search MCP

by flyanima

search_iacr

Search for cryptography research papers from the International Association for Cryptologic Research (IACR) to find academic publications on cryptographic topics.

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 main handler function for the 'search_iacr' tool. It takes a query and optional maxResults, simulates an IACR ePrint Archive search by generating mock cryptography paper results, and returns structured data or error.
    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
        };
      }
    }
  • The input schema for the 'search_iacr' tool, defining a required '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']
    },
  • The registration of the 'search_iacr' tool within the registerBioRxivTools function, including name, description, category, source, inputSchema, and execute handler.
    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
          };
        }
      }
    });
  • src/index.ts:233-233 (registration)
    The call to registerBioRxivTools in the main server initialization, which registers the 'search_iacr' tool among others.
    registerBioRxivTools(this.toolRegistry);            // 3 tools: search_iacr, search_medrxiv, search_biorxiv
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Search' implies a read-only operation, the description doesn't mention rate limits, authentication requirements, result format, pagination behavior, or any constraints beyond what's implied by the name. This is inadequate for a search tool with zero annotation coverage.

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 states the tool's purpose without unnecessary words. It's appropriately sized for a search tool and front-loads the essential information.

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 no annotations and no output schema, the description is insufficient. It doesn't explain what the search returns (papers, authors, conferences?), how results are formatted, whether there are limitations (date ranges, publication types), or how it differs from other search tools in the sibling list.

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 both parameters thoroughly. The description adds no additional parameter information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 action ('Search') and target resource ('IACR for cryptography papers'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from sibling search tools like search_arxiv or search_pubmed, which would require explicit differentiation to earn a 5.

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 multiple search tools available (search_arxiv, search_pubmed, search_semantic_scholar, etc.), there's no indication of what makes IACR searches unique or when they're preferred over other research databases.

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