Skip to main content
Glama

gutenberg-mcp-server

by io.github.cyanheads

Search Gutenberg Books

gutenberg_search_books
Read-onlyIdempotent

Search the Project Gutenberg catalog of 78,000+ public-domain books. Matches title and author name with query words; filters by topic (subject or bookshelf keyword), language, author lifespan, or a specific list of Gutenberg IDs. Results are ordered by popularity (download count) by default. Returns book ID, title, authors, languages, subjects, and download count — use gutenberg_get_book for the full formats map before fetching text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoNarrow results to specific Gutenberg ID numbers. Other filters still apply. Useful for batch pre-fetching known IDs; use gutenberg_get_book for single-ID lookups.
pageNoPage number for paginated results (1-indexed). Each page returns up to 32 books. Use totalCount to determine total pages.
sortNoResult ordering. "popular" (default) sorts by download count descending. "ascending" and "descending" sort by Gutenberg ID number.popular
queryNoWords to match against book titles and author names (case-insensitive, space-separated). Example: "dickens expectations" matches Great Expectations by Charles Dickens.
topicNoCase-insensitive phrase to match against subjects and bookshelves. Example: "detective" returns books on the "Detective and Mystery Stories" bookshelf. Separate from query — topic searches categorization metadata, not title/author.
languagesNoFilter to books in any of these two-character ISO 639-1 language codes. Example: ["en"] for English, ["fr", "de"] for French or German.
author_year_endNoInclude only books with at least one author alive on or before this year. Example: author_year_start=1800 with author_year_end=1899 returns books with 19th-century authors.
author_year_startNoInclude only books with at least one author alive on or after this year (positive = CE, negative = BCE). Combine with author_year_end for a range.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoCurrent page number.
booksNoMatching books, ordered by the sort parameter.
errorNoPresent when the call failed. Absent on success.
hasMoreNoTrue if there are additional pages of results.
totalCountNoTotal number of books matching the query across all pages.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations (readOnlyHint, openWorldHint, idempotentHint) already convey the operation is safe and non-mutating. The description adds behavioral details: it matches title/author, applies filters, orders by download count by default, and returns a specific set of fields. No contradiction exists, and the added context is useful for the caller.

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?

The description is a single, information-dense sentence with no wasted words. It front-loads the primary action and purpose, then lists filters and output details. Every clause contributes to the agent's understanding.

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?

The description covers the search scope, default ordering, returned fields, and a pointer to a sibling for extended data. With an output schema present and all 8 parameters documented in the schema, nothing essential is missing for an agent to invoke the tool correctly.

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?

The schema description coverage is 100%, so each parameter is already well-documented in the input schema. The tool description repeats some high-level filter concepts but does not add meaning beyond the schema. With complete schema coverage, a score of 3 is appropriate per the calibration guidelines.

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 states a specific verb ('Search'), a target resource ('Project Gutenberg catalog'), and the scope ('78,000+ public-domain books'). It enumerates the matching and filtering capabilities, and points to a sibling (gutenberg_get_book) for a different purpose. This clearly distinguishes it from the other tools in the group.

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?

The description provides clear usage context: it is for searching and filtering, with default ordering and a pointer to gutenberg_get_book for full format maps. However, it does not explicitly state when to prefer gutenberg_browse_popular or when not to use this tool, though the search-focused wording implies those exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All gutenberg-mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool has a clear, distinct purpose: browse popular books, fetch metadata, retrieve text, and search the catalog. No overlap or ambiguity between them.

Naming Consistency5/5

All tools follow the consistent pattern of 'gutenberg_' prefix followed by a descriptive verb and noun (browse_popular, get_book, get_text, search_books). The naming is uniform and predictable.

Tool Count5/5

Four tools is well-scoped for a Project Gutenberg server, covering essential operations without unnecessary bloat. The count is ideal for the domain.

Completeness5/5

The surface covers the full read-only lifecycle: discovery (browse and search), metadata retrieval (get_book), and content access (get_text). No gaps are evident for the intended use case.

Resources