Scholar MCP Server

interact_with_book_tool

Extract table of contents, search for keywords, or retrieve text from specific page ranges using a book's Libgen MD5 hash.

Instructions

Extract text or interact with a book using its Libgen MD5 hash. action:

'toc': Returns the table of contents.
'search': Searches for 'keyword' and returns only pages where it is found.
'pages': Extracts text strictly from 'start_page' to 'end_page'.

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": {
      "md5": "<md5>"
    },
    "name": "interact_with_book_tool"
  }
}

Input Schema

Name	Required	Default
`md5`	Yes
`action`	No	toc
`keyword`	No
`end_page`	No
`start_page`	No

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?

With no annotations, the description effectively explains the behavior of each action: returns TOC, searches for keyword returning only found pages, extracts text from start_page to end_page. It adds context beyond the schema but could be improved by mentioning error handling or limitations (e.g., invalid md5).

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 very concise and well-structured, using a brief introductory sentence followed by a bullet list. Every sentence adds value, and the overall length is appropriate for the complexity.

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?

Given the 5 parameters (1 required), no annotations, and existing output schema, the description covers the key behaviors for the actions. The missing explanation for 'md5' is a minor gap. Overall, it is sufficiently complete for an agent to use the tool correctly.

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 0%, so the description must compensate. It explains the 'action' parameter and its values, and contextualizes 'keyword', 'start_page', 'end_page'. However, the required 'md5' parameter is only mentioned vaguely in the first line without detailed semantics (e.g., format, length). This leaves a gap.

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 tool's purpose: 'Extract text or interact with a book using its Libgen MD5 hash.' It enumerates specific actions (toc, search, pages) making it distinct from sibling tools like search_books or get_book_details.

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

Usage Guidelines4/5

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

The description provides clear guidance on when to use each action (e.g., 'toc' for table of contents, 'search' with a keyword, 'pages' for a page range). However, it does not explicitly state when not to use this tool or suggest alternatives, leaving some implicit inference to the agent.

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