Skip to main content
Glama
Sign In
calibre-mcp

calibre-mcp

by caelum29
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Open book in local viewer (widget-internal)

calibre_open_book
Read-only

Launches a book in the local Calibre viewer using its calibre:// link, enabling immediate reading from the chat interface.

Instructions

Internal endpoint for the in-chat widgets' Open button. Launches a book in the local Calibre viewer via the calibre:// scheme. Do not call as the model — use calibre_get_book to show a book instead.

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": {
      "id": "<id>"
    },
    "name": "calibre_open_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
formatNo
libraryNo

Output Schema

NameRequiredDescriptionDefault
urlYes
formatYes
openedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true. The description adds that it is an internal endpoint and launches a viewer via a URI scheme, providing additional context beyond the annotations. No contradictions.

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 sentences, front-loaded with purpose, followed by an explicit usage directive. No redundant information; every sentence serves a purpose.

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?

Given the tool's simplicity, annotations cover behavioral safety, and an output schema exists (so return values are documented elsewhere). The description lacks parameter explanations, but the main usage context is well-covered.

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

Parameters2/5

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

Schema description coverage is 0%, and the description provides no information about the three parameters (id, format, library). Agents must infer meaning solely from names and types, which is insufficient for proper invocation.

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?

The description clearly states it launches a book in the local Calibre viewer via the calibre:// scheme. It distinguishes itself from the sibling tool calibre_get_book by specifying it is internal for widget buttons.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance: 'Do not call as the model — use calibre_get_book to show a book instead.' This tells the agent both when not to use it and what alternative to use.

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