Skip to main content
Glama
flyanima

Open Search MCP

by flyanima

search_biorxiv

Search bioRxiv preprints using keywords, filter by category and date range, and sort by relevance, date, or citations. Access biology and life sciences research.

Instructions

Search bioRxiv for biology and life sciences preprints

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query for bioRxiv papers (e.g., "CRISPR", "COVID-19", "neuroscience", "cancer research")
maxResultsNoMaximum number of papers to return (1-100)
categoryNobioRxiv category filter
dateFromNoStart date for filtering (YYYY-MM-DD format)
dateToNoEnd date for filtering (YYYY-MM-DD format)
sortNoSort order: relevance, date, citationsrelevance
Behavior2/5

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

No annotations provided. Description does not disclose any behavioral traits beyond a generic search capability, lacking details on authentication, rate limits, or return structure.

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?

Single sentence, no redundancy. Efficient but could benefit from a brief example or use case.

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?

With 6 parameters and no output schema or annotations, the description is too minimal. Lacks explanation of return format, pagination, or search behavior, making it feel incomplete.

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 baseline of 3 is appropriate. Description adds no additional meaning beyond what is already in the schema.

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?

Description specifies exact verb 'Search' and resource 'bioRxiv' with domain 'biology and life sciences preprints'. Distinguishes from sibling tools like search_medrxiv and search_arxiv.

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 on when to use this tool versus alternatives such as search_pubmed or search_semantic_scholar. The description does not provide context for selection.

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