calibre-mcp

Overview Schema Source Related Servers Discussions Admin

Quality report

calibre_quality_report

Read-only

Scan a Calibre library for missing metadata, invalid ISBNs, raw-filename titles, author-sort mismatches, and series gaps, returning a read-only quality report you can narrow by IDs, query, or filter.

Instructions

Scan books for metadata problems: missing fields, raw-filename titles, invalid ISBNs, author-sort mismatches, series gaps. Defaults to the whole library; narrow with ids/query/filter (a bundle name) or specific checks. Read-only.

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_quality_report"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	No
`limit`	No
`query`	No
`checks`	No
`cursor`	No
`filter`	No
`library`	No
`readability`	No

Output Schema

Name	Required	Description	Default
`count`	No
`total`	No
`capped`	No
`issues`	No
`offset`	No
`byCheck`	No
`nextCursor`	No
`booksScanned`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.10.0Oct 28, 2026

changedInput schema / properties / checks / items / enum

Previous value: -[
-  "missing_metadata",
-  "raw_filename_title",
-  "isbn_invalid",
-  "author_sort_mismatch",
-  "series_gaps"
-]New value: +[
+  "missing_metadata",
+  "raw_filename_title",
+  "isbn_invalid",
+  "author_sort_mismatch",
+  "series_gaps",
+  "authors_suspect"
+]

addedOutput schema / properties / issues

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "bookId": {
+        "type": "number"
+      },
+      "check": {
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "severity": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "bookId",
+      "title",
+      "check",
+      "severity",
+      "message"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedv0.7.3Aug 18, 2026
- addedInput schema / properties / filter
```
Added value: +{
+  "maxLength": 256,
+  "minLength": 1,
+  "type": "string"
+}
```
First observedv0.7.2Jul 29, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description's 'Read-only' merely restates that rather than adding new context. It does disclose the important default scope (whole library), but says nothing about result volume or pagination despite offering limit and cursor.

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 dense sentences, front-loaded with the purpose and followed by the scoping rules. No filler and nothing restated from the title.

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

Completeness3/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 explained. But for an 8-parameter tool with zero schema description coverage, leaving pagination (limit/cursor), library selection, and readability unexplained is a real gap in an otherwise solid definition.

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 coverage is 0%, so the description carries the full burden, and it only partially delivers: ids/query and filter (clarified usefully as 'a bundle name') and checks are covered. Four parameters — limit, cursor, library, readability — are left entirely undefined for the agent.

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 ('Scan books') and resource ('metadata problems'), then enumerates the concrete check classes (raw-filename titles, invalid ISBNs, series gaps). An agent can tell this apart from calibre_recover_metadata or calibre_find_duplicates from the description alone.

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?

Gives clear operating context: default is the whole library, and narrowing happens via ids/query/filter or specific checks. It doesn't name an explicit alternative tool for the fixing workflow (e.g. calibre_recover_metadata), so it stops 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