Skip to main content
Glama
Sign In
Paper Search MCP

Paper Search MCP

by openags
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

read_medrxiv_paper

Extract text content from medRxiv paper PDFs using DOI identifiers for analysis and research purposes.

Instructions

Read and extract text content from a medRxiv paper PDF.

Args: paper_id: medRxiv DOI. save_path: Directory where the PDF is/will be saved (default: './downloads'). Returns: str: The extracted text content of the paper.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "paper_id": "<paper_id>"
    },
    "name": "read_medrxiv_paper"
  }
}

Input Schema

NameRequiredDescriptionDefault
paper_idYes
save_pathNo./downloads

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.5/5.0
Behavior2/5

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

The description discloses the basic action (read and extract text) but does not specify behavioral traits such as whether it downloads the PDF locally, any side effects, authentication requirements, or rate limits. With no annotations, the description is insufficient for full transparency.

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 extremely concise with two sentences plus parameter bullets. There is no redundancy or unnecessary information, and the structure is front-loaded with the core action.

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

Completeness3/5

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

The description covers the basic function and parameter details, but lacks completeness regarding error scenarios, output format intricacies, and the relationship to sibling tools. Given the presence of an output schema (not shown), the return value is partially addressed.

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

Parameters4/5

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

Both parameters are explained: paper_id is described as a medRxiv DOI, and save_path is described as a directory with a default value. Since the input schema has 0% description coverage, the description effectively compensates by adding missing meaning.

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 clearly states the verb 'Read and extract' and the resource 'medRxiv paper PDF', and the paper_id parameter specifies it's a medRxiv DOI, distinguishing it from sibling read_*_paper tools for other sources.

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 is provided on when to use this tool versus alternatives like read_arxiv_paper or download_medrxiv. The agent is left to infer based solely on the tool name, with no explicit usage context or exclusions.

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

Deploy Server

Other Tools