Skip to main content
Glama

FoxAPIs data sources

bioRxiv preprints

biorxiv_preprints
Read-onlyIdempotent

Recent preprints from bioRxiv or medRxiv by keyword or DOI: title, authors, date, category and link. Costs 5 credits a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "biorxiv_preprints"
  }
}

Input Schema

NameRequiredDescriptionDefault
doiNo
queryNoFor example: "protein folding"
serverNobiorxiv
days_backNo
max_resultsNoFor example: 3

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely non-structured context: the 5-credit cost, the no-charge policy when no data is returned, and the API-key requirement — all of which affect whether and how an agent should call it.

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?

Three tight clauses: what it returns, what it costs, what credentials it needs. Purpose is front-loaded and every clause carries information an agent needs; no filler.

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?

With no output schema, the description usefully enumerates return fields, and it covers cost and authentication. Minor gaps remain: no mention of result-count behavior (max_results), the server default, or how days_back interacts with an explicit DOI lookup.

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 coverage is 40%, so the description must compensate. It maps 'keyword' to query, 'DOI' to doi, 'bioRxiv or medRxiv' to server, and 'Recent' to days_back, which covers most undocumented params at a high level, but gives no defaults, syntax, or meaning for max_results beyond what the schema states. 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?

States a specific verb+resource ('Recent preprints from bioRxiv or medRxiv') and the two retrieval modes (keyword or DOI), plus the returned fields. It is distinguishable from pubmed_search and academic_paper by source, though it does not explicitly contrast with those siblings.

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

Usage Guidelines3/5

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

The 'by keyword or DOI' phrasing implies both invocation paths, but there is no explicit when-to-use versus a sibling like pubmed_search or academic_paper, and no guidance on when DOI lookup is preferable to a keyword query. Usage is inferable rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources