Skip to main content
Glama
Sign In
Book Downloader MCP

Book Downloader MCP

by Abhinav-Prabhakar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Check mirror health

libgen_status
Read-onlyIdempotent

Probe every configured LibGen mirror with a real search request and report latency and errors. Use it to diagnose failures when searches stop working.

Instructions

Probe every configured mirror with a real search request and report latency and errors. Use this when searches fail.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "libgen_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive, so safety is covered. The description adds real value by disclosing that it issues an actual search against every mirror (implying cost and latency) and that results include latency and errors, though it does not mention timeouts or expected duration.

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 tight sentences with the action front-loaded and the usage trigger second; no wording is wasted.

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 zero parameters, rich annotations, and no output schema, the description is nearly complete for this tool's complexity. It names what is reported (latency and errors) but gives no sense of result shape or how long a full sweep takes.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. No parameter semantics are needed or missing.

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: probing every configured mirror with a real search request and reporting latency and errors. This naturally distinguishes it from libgen_list_mirrors (which lists rather than probes) and libgen_set_mirror, though no sibling is named explicitly.

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?

'Use this when searches fail' gives a concrete trigger condition for invoking the tool. It offers no exclusions or explicit alternatives such as calling list_mirrors first, so it falls short of full when/when-not guidance.

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