Skip to main content
Glama
Liyux3

scholar-mcp

by Liyux3

read_paper

Download a paper's PDF using its identifier (S2 ID, DOI, ArXiv ID) and extract text content when needed.

Instructions

Download a paper's PDF and optionally extract its text content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paper_idYesPaper identifier (S2 ID, DOI, ArXiv:ID, etc.)
save_dirNoDirectory to save PDF (default: configured download directory)
max_pagesNoMaximum pages to extract (0 = all pages)
extract_textNoIf True, extract and return text. If False, just download PDF.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so description carries full burden. It mentions download and optional text extraction but lacks details on file sizes, rate limits, authentication, or error handling. Adequate but not thorough.

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?

Single sentence, front-loaded with action, no unnecessary words. Highly concise.

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 output schema present and low parameter count (4), the description covers the core functionality. However, it omits details about extraction failure scenarios or supported paper_id formats, leaving some completeness gaps.

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 100%, so parameters are fully described. The description adds no extra meaning beyond the schema fields; it does not clarify paper_id formats or default behaviors beyond what schema provides.

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 clearly states verb+resource: 'Download a paper's PDF' with optional text extraction. Distinguishes from sibling tools like 'search_papers' or 'paper_info' which are for searching or retrieving metadata.

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?

Description implies usage for downloading/extracting papers but does not provide explicit when-to-use or when-not-to-use guidance, nor alternatives among sibling tools.

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/Liyux3/scholar-mcp'

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