Skip to main content
Glama
Sign In
calibre-mcp

calibre-mcp

by caelum29
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Calibre ping

calibre_ping
Read-only

Checks MCP server access to Calibre Content Server via calibredb and reports semantic-search coverage, version, write-gate state, busy libraries, recent errors, and log path for diagnosis.

Instructions

Health check: confirms the MCP server can reach the running Calibre Content Server via calibredb, and reports semantic-search status (embedding model, dependency, per-library index coverage). Returns the server version, calibredb path and write-gate state, plus libraries currently marked busy after a Calibre timeout, the server's recent errors and its log file path for self-diagnosis.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial behavioral context beyond them — it is non-mutating, it probes an external running server, and it enumerates what comes back (server version, calibredb path, write-gate state, libraries stuck busy after a timeout, recent errors, log path). It stops short of saying what happens on failure (does it throw, or return a degraded report?), which is the one gap worth closing.

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?

A single sentence, front-loaded with 'Health check:' so the agent knows the category before reading detail, and every clause maps to a distinct reported signal. Nothing is redundant.

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 parameters and no output schema, the description carries the full burden and does so by enumerating the returned fields, which is exactly what an agent needs to interpret results. The only missing piece is failure semantics — whether connection failure raises an error or yields a report indicating unreachable.

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 no parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly does not waste space on parameter talk and instead spends it on outcomes.

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 and resource — a health check that verifies the MCP server can reach the Calibre Content Server via calibredb — plus the semantic-search status it reports. This is clearly a diagnostic tool, distinguishable at a glance from every sibling (list, search, index, quality report), none of which probe connectivity.

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: 'Health check' and 'for self-diagnosis' suggest running it when something appears broken, but it never says when to prefer it over calibre_quality_report for health assessment or what to do with the result. No exclusions or prerequisites are given, leaving the agent to infer context.

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