Skip to main content
Glama
flyanima

Open Search MCP

by flyanima

search_medrxiv

Search medical preprints and clinical research on medRxiv to find relevant studies and papers for healthcare professionals and researchers.

Instructions

Search medRxiv for medical preprints and clinical research

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query for medical preprints
maxResultsNoMaximum number of results to return

Implementation Reference

  • The main handler function for the 'search_medrxiv' tool. It takes a query and optional maxResults, generates simulated medRxiv medical preprint search results, and returns structured data or error.
    execute: async (args: ToolInput): Promise<ToolOutput> => {
      try {
        const { query, maxResults = 20 } = args;
    
        // Simulated medRxiv search results
        const results = Array.from({ length: Math.min(maxResults, 10) }, (_, i) => ({
          title: `Clinical Study on ${query} - Research ${i + 1}`,
          authors: [`Dr. Medical Researcher ${i + 1}`, `Prof. Clinical Expert ${i + 1}`],
          abstract: `This clinical study investigates ${query} and its implications for patient care...`,
          date: new Date(2024, 0, i + 1).toISOString().split('T')[0],
          doi: `10.1101/2024.01.${String(i + 1).padStart(2, '0')}.24300001`,
          url: `https://www.medrxiv.org/content/10.1101/2024.01.${String(i + 1).padStart(2, '0')}.24300001v1`,
          category: 'Medical Research',
          keywords: [query, 'clinical', 'medical', 'preprint']
        }));
    
        return {
          success: true,
          data: {
            source: 'medRxiv',
            query,
            results,
            totalResults: results.length
          },
          metadata: {
            searchTime: Date.now(),
            source: 'medRxiv Preprint Server'
          }
        };
      } catch (error) {
        return {
          success: false,
          error: `medRxiv search failed: ${error instanceof Error ? error.message : String(error)}`,
          data: null
        };
      }
    }
  • Input schema defining the parameters for the search_medrxiv tool: required 'query' string and optional 'maxResults' number (1-100, default 20).
    inputSchema: {
      type: 'object',
      properties: {
        query: {
          type: 'string',
          description: 'Search query for medical preprints'
        },
        maxResults: {
          type: 'number',
          description: 'Maximum number of results to return',
          default: 20,
          minimum: 1,
          maximum: 100
        }
      },
      required: ['query']
    },
  • The registry.registerTool invocation that defines, configures, and registers the 'search_medrxiv' tool within the registerBioRxivTools function.
    registry.registerTool({
      name: 'search_medrxiv',
      description: 'Search medRxiv for medical preprints and clinical research',
      category: 'academic',
      source: 'medRxiv',
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: 'Search query for medical preprints'
          },
          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 medRxiv search results
          const results = Array.from({ length: Math.min(maxResults, 10) }, (_, i) => ({
            title: `Clinical Study on ${query} - Research ${i + 1}`,
            authors: [`Dr. Medical Researcher ${i + 1}`, `Prof. Clinical Expert ${i + 1}`],
            abstract: `This clinical study investigates ${query} and its implications for patient care...`,
            date: new Date(2024, 0, i + 1).toISOString().split('T')[0],
            doi: `10.1101/2024.01.${String(i + 1).padStart(2, '0')}.24300001`,
            url: `https://www.medrxiv.org/content/10.1101/2024.01.${String(i + 1).padStart(2, '0')}.24300001v1`,
            category: 'Medical Research',
            keywords: [query, 'clinical', 'medical', 'preprint']
          }));
    
          return {
            success: true,
            data: {
              source: 'medRxiv',
              query,
              results,
              totalResults: results.length
            },
            metadata: {
              searchTime: Date.now(),
              source: 'medRxiv Preprint Server'
            }
          };
        } catch (error) {
          return {
            success: false,
            error: `medRxiv search failed: ${error instanceof Error ? error.message : String(error)}`,
            data: null
          };
        }
      }
    });
  • src/index.ts:233-233 (registration)
    Invocation of registerBioRxivTools in the main server initialization (registerAllTools method), which registers the search_medrxiv tool among others.
    registerBioRxivTools(this.toolRegistry);            // 3 tools: search_iacr, search_medrxiv, search_biorxiv
  • src/index.ts:359-359 (registration)
    The search_medrxiv tool is explicitly listed in the README_33_TOOLS array used for filtering to exactly 33 tools in production.
    'search_iacr', 'search_biorxiv', 'search_medrxiv',
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 it indicates a search operation, it doesn't describe what kind of results are returned, whether there are rate limits, authentication requirements, or any behavioral characteristics beyond the basic search function. The description is minimal and lacks operational context.

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 immediately conveys the core function. There's no wasted language or unnecessary elaboration, making it optimally concise while still communicating the essential purpose.

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 insufficiently complete. It doesn't explain what format results are returned in, what fields are included, whether there's pagination, or any other operational details needed for effective use. The minimal description leaves too many unanswered questions.

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 fully documents both parameters. The description doesn't add any parameter-specific information beyond what's already in the schema descriptions. This meets the baseline expectation when schema coverage is complete.

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 ('medRxiv for medical preprints and clinical research'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like search_arxiv or search_biorxiv, which perform similar searches on different preprint 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 like search_arxiv, search_biorxiv, or search_pubmed. There's no mention of specific use cases, prerequisites, or comparative advantages for medRxiv searches versus 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