Scholar MCP Server

search_libgen_tool

Search Library Genesis for books and retrieve their MD5 hashes to enable full-text extraction and analysis.

Instructions

Search for books in Library Genesis (Libgen). Returns books with their 'md5' which can be used to extract the text. BEST PRACTICE: To know what a book is about before downloading, ALWAYS use 'search_books_tool' (Open Library/Google Books) FIRST to read its synopsis/description. Once you decide which book is best, use this tool to find its MD5 for text extraction.

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": {
      "query": "<query>"
    },
    "name": "search_libgen_tool"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations provided, so description carries burden. Reveals it searches and returns MD5 for text extraction. Could mention pagination or error states but adequate for a search tool.

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?

Two short sentences plus a brief best practice. Front-loaded with purpose, no fluff. Every sentence adds value.

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?

Output schema exists so return values are covered. Purpose and guidelines are strong, but missing parameter documentation for limit leaves a gap. Adequate but not comprehensive.

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

Parameters2/5

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

Schema coverage is 0% and description only implicitly references 'query' via 'search for books'. Does not explain 'limit' parameter. Fails to add meaning beyond 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?

Clearly states 'Search for books in Library Genesis (Libgen).' Verb+resource+context. Differentiates from sibling 'search_books_tool' by noting that tool is for synopsis first.

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?

Explicit BEST PRACTICE section: 'ALWAYS use search_books_tool FIRST... Once you decide which book is best, use this tool to find its MD5.' Provides clear when-to-use and when-not-to-use guidance.

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