Book Downloader MCP

Download several books

libgen_bulk_download

Download a batch of ebook files from a list of MD5 hashes with bounded concurrency; failures are reported per item so one bad hash does not abort the batch.

Instructions

Download a list of md5s with bounded concurrency. Failures are reported per item; one bad md5 does not abort the batch.

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": {
      "md5List": "<md5List>"
    },
    "name": "libgen_bulk_download"
  }
}

Input Schema

Name	Required	Description
`md5List`	Yes	Between 1 and 20 md5 hashes to download.
`overwrite`	No	Overwrite existing files.
`concurrency`	No	Parallel downloads (1-5). Defaults to 2.
`downloadDir`	No	Directory to save into.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.0.1Nov 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, but they cannot express partial-failure semantics. The description adds genuine value: failures are reported per item and one bad md5 does not abort the batch, which directly tells the agent how to interpret a mixed result.

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 with zero filler, and the core capability is front-loaded before the failure-semantics detail. Every clause carries information an agent needs.

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?

For a 4-parameter batch tool with no output schema, the per-item failure disclosure covers the main unknown — what happens when part of the batch fails. Gaps remain: it does not say what a successful item returns (path, URL, or status) or how overwrite interacts with existing files, but these are minor given full schema coverage and annotations.

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 100%, so md5List bounds, concurrency range, overwrite, and downloadDir are already fully documented in the schema. The description only restates the concurrency concept ('bounded concurrency') and adds no format, default, or interaction detail beyond what structured fields provide.

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 and resource ('Download a list of md5s') and adds the batch scope plus bounded concurrency, which implicitly distinguishes it from the singular libgen_download sibling. It never names that sibling, but the plural/one-of-many framing is unambiguous.

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?

Usage is implied by the bulk framing — an agent can infer this is for multiple md5s while libgen_download handles one — but there is no explicit when-to-use or when-not statement, and no mention of tradeoffs (e.g. prefer the single tool for one item).

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

Deploy Server