annas-mcp

Overview Schema Source Related Servers Discussions Admin

Download book

book_download

Download a book by MD5 hash or Anna's Archive /md5/ URL; reuse a matching local file or save a verified copy, returning its path and size.

Instructions

Download the selected book using its MD5 hash or Anna's Archive /md5/ page URL in hash. Returns an existing file in ANNAS_DOWNLOAD_PATH if its full MD5 matches, otherwise downloads a verified copy under a unique name. Returns path and bytes; downloads_left is omitted on local reuse. Format sets the extension; it does not convert the file.

Input Schema

Name	Required	Description
`hash`	Yes	32-character MD5 hash or Anna's Archive /md5/ page URL
`title`	Yes	Book title used for the filename
`format`	No	Optional filename extension such as pdf or epub. Inferred when omitted; does not convert the file
`timeout_seconds`	No	Total operation timeout in seconds, including retries. Defaults to 1800; maximum 86400

Output Schema

Name	Required	Description	Default
`path`	Yes
`bytes`	Yes
`downloads_left`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.7.0Oct 14, 2026

changedInput schema / properties / hash / description

Previous value: -"32-character MD5 hash from search"New value: +"32-character MD5 hash or Anna's Archive /md5/ page URL"

addedOutput schema / properties / downloads_left

Added value: +{
+  "type": [
+    "null",
+    "integer"
+  ]
+}

First observedv0.1.0Sep 29, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond annotations by disclosing the local-reuse behavior (returns an existing file when the full MD5 matches), verified downloading under a unique name, that path and bytes are returned, and that downloads_left is omitted on local reuse. This is the kind of behavioral detail an agent could not get from the structured fields alone.

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?

Front-loads the core action and inputs in the first sentence, then layers return behavior and the format caveat. Every sentence carries distinct information with no filler.

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?

An output schema exists so return values needn't be enumerated, yet the description still usefully characterizes the response and its conditional field. It omits failure modes (unavailable book, exhausted quota, timeout expiry), which is the only meaningful gap for a tool with retries and a 24h max timeout.

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 the baseline is 3. The description restates the hash input forms and the format-does-not-convert rule already present in the schema, but adds no syntax or edge-case detail (e.g. timeout behavior or format inference rules) beyond it.

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?

States a specific verb (download) and resource (the selected book) and specifies the exact input forms accepted (32-char MD5 or Anna's Archive /md5/ page URL). This clearly separates it from siblings like article_download and book_search without needing schema inspection.

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?

The phrase 'the selected book' implies a prior selection step (e.g. book_search/book_details) must happen first, but no alternative tool is named and no explicit when-not condition is given. Usage is inferable but not spelled out.

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

Deploy Server