Skip to main content
Glama
Sign In
Book Downloader MCP

Book Downloader MCP

by Abhinav-Prabhakar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Search LibGen

libgen_search
Read-onlyIdempotent

Search Library Genesis (LibGen+) for books and papers by title, author, or ISBN, returning metadata and detail-page URLs with automatic mirror rotation.

Instructions

Search Library Genesis (LibGen+) for books and papers. Returns title, authors, year, language, size, extension, md5 and the detail page URL. Mirrors are discovered automatically and rotated on failure.

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": "libgen_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page. Defaults to 1.
queryYesSearch terms, e.g. an author, title or ISBN.
pageSizeNoResults per page (1-100). Defaults to 25.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive semantics, so the safety profile is covered. The description adds genuine context beyond them: the exact result fields and the fact that mirrors are auto-discovered and rotated on failure, which tells the agent to expect resilience without manual mirror selection.

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?

Three short sentences, front-loaded with what it searches, then the returned fields, then the mirror behavior. Nothing is redundant and nothing needs trimming.

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 no output schema, the description usefully enumerates the return fields, and it covers the mirror subtlety that an agent would otherwise have to discover. It stops short of explaining how results feed into the download siblings, but that is a minor omission for a simple three-parameter search.

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%, with query, page and pageSize all documented including bounds and defaults, so the baseline is 3. The description adds no extra meaning about the query syntax or pagination behavior beyond what the schema already says.

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: searching Library Genesis (LibGen+) for books and papers, and enumerates what is returned. It is clearly distinct from the download and mirror-management siblings in practice, but the description itself never names a sibling or draws the boundary explicitly.

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 only implied by the purpose statement – an agent can infer this is the discovery step before libgen_download or libgen_get_download_url, but no when-to-use/when-not guidance or alternative routing is stated.

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

Deploy Server

Other Tools