Skip to main content
Glama
Sign In
calibre-mcp

calibre-mcp

by caelum29
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Calibre libraries

calibre_list_libraries
Read-only

Lists all Calibre libraries available on the Content Server and identifies the default one. Use it first to discover valid library names before querying or managing ebooks.

Instructions

List the Calibre libraries available on the Content Server and which one is the default. Call this first to discover valid library names.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
defaultNo
librariesNo
defaultUnavailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.0
    • addedOutput schema / properties / defaultUnavailable
      Added value: +{
+  "type": "string"
+}
  2. First observedv0.7.2

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds that the response tells you which library is the default, which is behavioral value beyond the annotations. It says nothing about failure modes if the server is unreachable, but nothing is contradicted.

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: what it returns, then when to call it. The purpose is front-loaded and every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter discovery tool with an output schema (which documents the returned library/default fields) and read-only annotations, the description supplies everything the agent needs: what it does, what it reveals, and that it should be called before other library-scoped tools.

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 per the baseline this scores 4. There is no parameter semantics to add, and the description correctly avoids inventing any.

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?

Specific verb+resource: 'List the Calibre libraries available on the Content Server', plus the extra detail that it reports the default library. This is clearly distinguished from siblings like calibre_search or calibre_get_book, which operate on books rather than library enumeration.

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?

'Call this first to discover valid library names' gives an explicit sequencing rule and states the payoff (obtaining names other tools need). It doesn't name a specific alternative to use instead, but for a zero-param discovery call there is little ambiguity to resolve.

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