Skip to main content
Glama
h-lu

Paper Search MCP Server

by h-lu

search_biorxiv

Search bioRxiv preprints by biology category (e.g., neuroscience, cell biology) to find research before peer review. Returns recent preprints with DOIs for download or reading.

Instructions

Search biology preprints on bioRxiv.

USE THIS TOOL WHEN:
- Searching for cutting-edge biology research (preprints)
- You need the latest findings before peer review
- Searching by CATEGORY, not keyword (see below)

DOMAIN: Molecular Biology, Cell Biology, Genetics, Neuroscience,
Bioinformatics, Evolutionary Biology, Microbiology, etc.

NOTE: bioRxiv search uses CATEGORY names, not keywords.
Categories: 'neuroscience', 'cell_biology', 'genetics', 'genomics',
'bioinformatics', 'cancer_biology', 'immunology', etc.

WORKFLOW:
1. search_biorxiv(category) -> get DOI
2. download_biorxiv(doi) or read_biorxiv_paper(doi)

Args:
    query: Category name (e.g., 'neuroscience', 'cell_biology').
    max_results: Number of results (default: 10).

Returns:
    List of recent preprints in that category.

Example:
    search_biorxiv("neuroscience", max_results=5)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
max_resultsNo
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the category-based query behavior and that results are 'recent preprints' but does not mention rate limits, pagination, or whether the tool is read-only. Does not contradict any annotations.

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?

Well-structured with USE THIS, DOMAIN, NOTE, WORKFLOW sections. The example and category list add value. Could be slightly tightened (e.g., reduce redundant phrases) but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations or output schema, the description covers purpose, usage, parameter semantics, and integration with sibling tools. It lacks detail on return format and behavioral traits like rate limits, but is largely complete for a search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but description adds thorough semantics: explains that query is a category name, provides a list of common categories, sets default for max_results, and includes an example. This compensates fully for the lack of schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifies 'Search biology preprints on bioRxiv', naming the resource and domain. It distinguishes from sibling search tools like search_arxiv or search_pubmed by focusing on bioRxiv, and notes category-based search.

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

Usage Guidelines5/5

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

Explicitly states when to use ('cutting-edge biology research', 'latest findings'), and critically highlights that search is by CATEGORY not keyword. Provides a workflow linking to sibling tools and lists example categories.

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/h-lu/paper-find-mcp'

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