Skip to main content
Glama

gutenberg-mcp-server

by io.github.cyanheads

Server Details

MCP server for Project Gutenberg — 75,000+ public-domain ebooks with full plain-text retrieval.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP
URL
Repository
cyanheads/gutenberg-mcp-server
GitHub Stars
2
Server Listing
gutenberg-mcp-server

Available Tools

4 tools
gutenberg_get_bookGet Gutenberg BookA
Read-onlyIdempotent
Inspect

Fetch complete metadata for a Project Gutenberg book by ID — title, authors (with birth/death years), translators, editors, subjects, bookshelves, languages, copyright status, and the full formats map with download URLs for each available format (plain text, HTML, EPUB, cover image, etc.). Use this before gutenberg_get_text to confirm a plain-text format is available and to get the direct download URL.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesProject Gutenberg book ID. Visible in Gutenberg URLs (e.g., gutenberg.org/ebooks/1342) and returned by gutenberg_search_books and gutenberg_browse_popular. Example: 1342 for Pride and Prejudice, 2600 for War and Peace.

Output Schema

ParametersJSON Schema
NameRequiredDescription
idNoGutenberg ID.
errorNoPresent when the call failed. Absent on success.
titleNoBook title.
authorsNoPrimary author(s).
editorsNoEditors, if any.
formatsNoMap of MIME type to download URL. Key types: "text/plain; charset=utf-8" (preferred for gutenberg_get_text), "text/html", "application/epub+zip", "image/jpeg" (cover). Not every format is present for every book.
summaryNoFirst entry of summaries — the primary auto-generated summary of the work, or null when Gutendex has none.
subjectsNoLibrary of Congress subject headings.
copyrightNoCopyright status: false = public domain in the USA, true = under copyright, null = unknown.
languagesNoTwo-character language codes for this edition.
summariesNoEvery summary Gutendex holds for this work, in upstream order. Usually one; some records carry a long and a short variant. Empty when there are none.
media_typeNo"Text" for readable books, "Sound" for audio books. Only "Text" books have plain-text content available for gutenberg_get_text.
bookshelvesNoProject Gutenberg bookshelf categories (e.g., "Best Books Ever Listings", "Category: Classics of Literature").
translatorsNoTranslators, if this is a translated work.
download_countNoTotal downloads — popularity signal.
has_plain_textNoTrue if media_type is "Text" AND a UTF-8 text/plain format ("text/plain; charset=utf-8") is present in formats — prerequisite for gutenberg_get_text.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering the safety profile. The description adds valuable behavior context by specifying what metadata is returned and that the tool is a preliminary step for retrieving text. This goes beyond the annotations, explaining the tool's role and output structure without contradicting any hints.

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 two sentences with no wasted words. The first sentence front-loads the main purpose and enumerates the returned fields concisely. The second sentence adds essential usage guidance. Every sentence earns its place, and the structure is clean and scannable.

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?

The tool has an output schema (as noted), so detailed return-value documentation is not required in the description. The description lists the key metadata fields and provides a clear use case. It is complete for a single-parameter read-only tool, though it doesn't explicitly mention the output schema's structure. Overall, nothing critical is missing for correct invocation.

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 description coverage is 100%, and the schema's description for the 'id' parameter is very detailed, including examples and how to obtain the ID. The tool description adds only minimal reinforcement ('by ID') and does not provide additional parameter semantics beyond the schema. Since the schema is comprehensive, the baseline of 3 is appropriate.

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 ('Fetch'), a specific resource ('complete metadata for a Project Gutenberg book by ID'), and enumerates the exact fields returned (title, authors, translators, editors, subjects, etc.). It clearly distinguishes itself from the sibling tools by focusing on a single book's metadata, and explicitly references gutenberg_get_text as a follow-up. This differentiates it without ambiguity.

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?

The description provides explicit usage guidance: 'Use this before gutenberg_get_text to confirm a plain-text format is available and to get the direct download URL.' This tells the agent when to invoke this tool and why, while implying that gutenberg_get_text is for the actual text content. It gives a clear workflow context.

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

gutenberg_get_textGet Gutenberg Book TextA
Read-onlyIdempotent
Inspect

Retrieve the plain-text content of a Project Gutenberg book, stripped of the standard license header and footer so the response contains only the literary work. For long works — novels routinely run 500KB–2MB — use offset and limit to read in chunks rather than fetching the whole book at once. The response reports totalChars and remainingChars for reliable pagination. Prefers UTF-8 plain text; falls back to an HTML edition converted to text; refuses audio books (media_type "Sound") with a clear error.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesProject Gutenberg book ID. Use gutenberg_search_books or gutenberg_get_book to find IDs. Example: 1342 for Pride and Prejudice, 2600 for War and Peace, 84 for Frankenstein.
limitNoMaximum number of characters to return in this chunk. Default 20,000 (~4–5 pages of prose). Increase toward 50,000 for large context windows. The actual returned length may be slightly less than limit when a natural paragraph boundary is found within 500 characters of the limit — check the length field in the response for the actual character count returned.
offsetNoCharacter offset into the stripped literary text at which to start reading. 0 returns the beginning of the work. To read subsequent chunks, use offset = prior_offset + prior_length (the length field from the previous response — NOT offset + limit, because the actual returned length may be slightly less than limit due to paragraph-boundary trimming).

Output Schema

ParametersJSON Schema
NameRequiredDescription
idNoGutenberg book ID.
textNoThe requested chunk of literary text, stripped of Gutenberg license boilerplate. Encoding: UTF-8. Line endings: normalized to LF.
errorNoPresent when the call failed. Absent on success.
titleNoBook title, from the catalog record.
lengthNoNumber of characters in this chunk.
offsetNoCharacter offset where this chunk begins.
hasMoreNoTrue if there is more text after this chunk. When true, call again with offset = offset + length.
provenanceNoOne-line source note with Project Gutenberg ID, title, and license URL.
totalCharsNoTotal characters in the stripped literary text. Use with offset and length to determine progress and plan subsequent calls.
sourceFormatNoThe format that was fetched. "text/html" indicates HTML-to-text conversion was applied because no plain-text format was available.
remainingCharsNoCharacters remaining after this chunk (totalChars - offset - length). 0 means this chunk includes the end of the book.

TDQS

A5/5.0
Behavior5/5

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

Annotations declare readOnly, openWorld, and idempotent hints, and the description adds substantial behavioral detail beyond that: stripping headers/footers, preferring UTF-8 plain text and falling back to HTML conversion, refusing audio books, and reporting totalChars/remainingChars for pagination. This is consistent with annotations and enriches the agent's understanding.

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 concise relative to the complexity, with each sentence carrying key information. It front-loads the core purpose, then provides practical usage details for chunking and pagination, and ends with fallback behaviors. There is no wasted wording; every sentence 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?

Given the tool's simplicity (only one required parameter) and the rich annotations and output schema, the description covers all necessary context: purpose, pagination mechanics, response fields, fallback behavior, and error cases. It is complete enough for an agent to call the tool correctly without further clarification.

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

Parameters5/5

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

The schema already covers 100% of parameters, and the description adds significant semantics, especially for offset: it explicitly states to use prior_offset + prior_length rather than offset + limit due to paragraph-boundary trimming, and explains the limit default and actual return length behavior. This goes well beyond the schema's descriptions.

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 the verb 'Retrieve' and the resource 'plain-text content of a Project Gutenberg book', and specifies the key distinguishing detail of stripping license headers/footers. It also differentiates from siblings by naming that book IDs come from gutenberg_search_books or gutenberg_get_book, making the purpose unambiguous.

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?

The description gives explicit guidance on when to use offset/limit for long works, explains pagination using totalChars/remainingChars, and notes it refuses audio books. It implies that for searching or getting book metadata, other tools should be used, effectively distinguishing this tool's usage context.

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

gutenberg_search_booksSearch Gutenberg BooksA
Read-onlyIdempotent
Inspect

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.

ParametersJSON 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

ParametersJSON Schema
NameRequiredDescription
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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 4 tool updates
    • Changedgutenberg_browse_popular2 fields changed
      • changedOutput schema / properties / error / properties / data / properties / reason / description
        Previous value: -"Machine-readable failure mode. Declared by this tool: `no_results`: No books match the language/topic filter combination. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `no_results`: No books match the language/topic filter combination. `catalog_unavailable`: The Project Gutenberg catalog did not answer within the time this server allows for one browse. Other values are possible when a failure originates below the handler."
      • changedOutput schema / properties / error / properties / data / properties / reason / examples
        Previous value: -[
-  "no_results"
-]New value: +[
+  "no_results",
+  "catalog_unavailable"
+]
    • Changedgutenberg_get_book5 fields changed
      • changedOutput schema / anyOf
        Previous value: -[
-  {
-    "not": {
-      "required": [
-        "error"
-      ]
-    },
-    "required": [
-      "id",
-      "title",
-      "authors",
-      "translators",
-      "editors",
-      "subjects",
-      "bookshelves",
-      "languages",
-      "copyright",
-      "media_type",
-      "download_count",
-      "summary",
-      "formats",
-      "has_plain_text"
-    ]
-  },
-  {
-    "required": [
-      "error"
-    ]
-  }
-]New value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "id",
+      "title",
+      "authors",
+      "translators",
+      "editors",
+      "subjects",
+      "bookshelves",
+      "languages",
+      "copyright",
+      "media_type",
+      "download_count",
+      "summary",
+      "summaries",
+      "formats",
+      "has_plain_text"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]
      • changedOutput schema / properties / error / properties / data / properties / reason / description
        Previous value: -"Machine-readable failure mode. Declared by this tool: `not_found`: No book exists with the given ID. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: No book exists with the given ID. `catalog_unavailable`: The Project Gutenberg catalog did not answer within the time this server allows for one lookup. Other values are possible when a failure originates below the handler."
      • changedOutput schema / properties / error / properties / data / properties / reason / examples
        Previous value: -[
-  "not_found"
-]New value: +[
+  "not_found",
+  "catalog_unavailable"
+]
      • addedOutput schema / properties / summaries
        Added value: +{
+  "description": "Every summary Gutendex holds for this work, in upstream order. Usually one; some records carry a long and a short variant. Empty when there are none.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
      • changedOutput schema / properties / summary / description
        Previous value: -"Auto-generated summary of the work, when available. Absent on many older records."New value: +"First entry of summaries — the primary auto-generated summary of the work, or null when Gutendex has none."
    • Changedgutenberg_get_text2 fields changed
      • changedOutput schema / properties / error / properties / data / properties / reason / description
        Previous value: -"Machine-readable failure mode. Declared by this tool: `not_found`: No book exists with the given ID. `audio_book`: The book is an audio recording (media_type \"Sound\"), not a text book — no literary plain text is available. `no_text_format`: The book has no UTF-8 plain-text or HTML edition available to read (for example an older ASCII-only entry). `offset_out_of_range`: The offset is greater than or equal to totalChars (past the end of the book). `text_fetch_failed`: The Gutenberg file server returned an error or did not respond within the timeout. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: No book exists with the given ID. `audio_book`: The book is an audio recording (media_type \"Sound\"), not a text book — no literary plain text is available. `no_text_format`: The book has no UTF-8 plain-text or HTML edition available to read (for example an older ASCII-only entry). `offset_out_of_range`: The offset is greater than or equal to totalChars (past the end of the book). `text_fetch_failed`: The Gutenberg file server returned an error or did not respond within the timeout. `catalog_unavailable`: The catalog lookup that precedes reading a book did not answer within the time this server allows. Other values are possible when a failure originates below the handler."
      • changedOutput schema / properties / error / properties / data / properties / reason / examples
        Previous value: -[
-  "not_found",
-  "audio_book",
-  "no_text_format",
-  "offset_out_of_range",
-  "text_fetch_failed"
-]New value: +[
+  "not_found",
+  "audio_book",
+  "no_text_format",
+  "offset_out_of_range",
+  "text_fetch_failed",
+  "catalog_unavailable"
+]
    • Changedgutenberg_search_books2 fields changed
      • changedOutput schema / properties / error / properties / data / properties / reason / description
        Previous value: -"Machine-readable failure mode. Declared by this tool: `no_results`: The query matched no books in the catalog. `page_out_of_range`: The requested page number is past the last page of results for this query. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `no_results`: The query matched no books in the catalog. `page_out_of_range`: The requested page number is past the last page of results for this query. `catalog_unavailable`: The Project Gutenberg catalog did not answer within the time this server allows for one search. Other values are possible when a failure originates below the handler."
      • changedOutput schema / properties / error / properties / data / properties / reason / examples
        Previous value: -[
-  "no_results",
-  "page_out_of_range"
-]New value: +[
+  "no_results",
+  "page_out_of_range",
+  "catalog_unavailable"
+]
  2. 4 tool updates
    • Changedgutenberg_browse_popular6 fields changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
      • addedInput schema / additionalProperties
        Added value: +false
      • changedOutput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
      • addedOutput schema / anyOf
        Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "books",
+      "totalInCatalog",
+      "truncated",
+      "shown",
+      "cap"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]
      • addedOutput schema / properties / error
        Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `no_results`: No books match the language/topic filter combination. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "no_results"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}
      • removedOutput schema / required
        Removed value: -[
-  "books",
-  "totalInCatalog",
-  "truncated",
-  "shown",
-  "cap"
-]
    • Changedgutenberg_get_book6 fields changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
      • addedInput schema / additionalProperties
        Added value: +false
      • changedOutput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
      • addedOutput schema / anyOf
        Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "id",
+      "title",
+      "authors",
+      "translators",
+      "editors",
+      "subjects",
+      "bookshelves",
+      "languages",
+      "copyright",
+      "media_type",
+      "download_count",
+      "summary",
+      "formats",
+      "has_plain_text"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]
      • addedOutput schema / properties / error
        Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `not_found`: No book exists with the given ID. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "not_found"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}
      • removedOutput schema / required
        Removed value: -[
-  "id",
-  "title",
-  "authors",
-  "translators",
-  "editors",
-  "subjects",
-  "bookshelves",
-  "languages",
-  "copyright",
-  "media_type",
-  "download_count",
-  "summary",
-  "formats",
-  "has_plain_text"
-]
    • Changedgutenberg_get_text6 fields changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
      • addedInput schema / additionalProperties
        Added value: +false
      • changedOutput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
      • addedOutput schema / anyOf
        Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "id",
+      "title",
+      "text",
+      "offset",
+      "length",
+      "totalChars",
+      "remainingChars",
+      "hasMore",
+      "provenance",
+      "sourceFormat"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]
      • addedOutput schema / properties / error
        Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `not_found`: No book exists with the given ID. `audio_book`: The book is an audio recording (media_type \"Sound\"), not a text book — no literary plain text is available. `no_text_format`: The book has no UTF-8 plain-text or HTML edition available to read (for example an older ASCII-only entry). `offset_out_of_range`: The offset is greater than or equal to totalChars (past the end of the book). `text_fetch_failed`: The Gutenberg file server returned an error or did not respond within the timeout. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "not_found",
+            "audio_book",
+            "no_text_format",
+            "offset_out_of_range",
+            "text_fetch_failed"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}
      • removedOutput schema / required
        Removed value: -[
-  "id",
-  "title",
-  "text",
-  "offset",
-  "length",
-  "totalChars",
-  "remainingChars",
-  "hasMore",
-  "provenance",
-  "sourceFormat"
-]
    • Changedgutenberg_search_books6 fields changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
      • addedInput schema / additionalProperties
        Added value: +false
      • changedOutput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
      • addedOutput schema / anyOf
        Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "books",
+      "totalCount",
+      "page",
+      "hasMore"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]
      • addedOutput schema / properties / error
        Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `no_results`: The query matched no books in the catalog. `page_out_of_range`: The requested page number is past the last page of results for this query. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "no_results",
+            "page_out_of_range"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}
      • removedOutput schema / required
        Removed value: -[
-  "books",
-  "totalCount",
-  "page",
-  "hasMore"
-]
  3. 3 tool updates
    • Changedgutenberg_browse_popular1 field changed
      • changedOutput schema / properties / books / items / properties / has_plain_text / description
        Previous value: -"True if media_type is \"Text\" AND a text/plain format is available via gutenberg_get_text."New value: +"True if media_type is \"Text\" AND a UTF-8 text/plain format is available via gutenberg_get_text."
    • Changedgutenberg_get_book1 field changed
      • changedOutput schema / properties / has_plain_text / description
        Previous value: -"True if media_type is \"Text\" AND a text/plain format (UTF-8 or ASCII) is present in formats — prerequisite for gutenberg_get_text."New value: +"True if media_type is \"Text\" AND a UTF-8 text/plain format (\"text/plain; charset=utf-8\") is present in formats — prerequisite for gutenberg_get_text."
    • Changedgutenberg_search_books1 field changed
      • changedOutput schema / properties / books / items / properties / has_plain_text / description
        Previous value: -"True if the book has media_type \"Text\" AND a text/plain format available — prerequisite for gutenberg_get_text."New value: +"True if the book has media_type \"Text\" AND a UTF-8 text/plain format available — prerequisite for gutenberg_get_text."
  4. 4 tool updates
    • First observedgutenberg_browse_popular
    • First observedgutenberg_get_book
    • First observedgutenberg_get_text
    • First observedgutenberg_search_books

Frequently Asked Questions

Discussions

No comments yet. Be the first to start the discussion!

Login with GitHub to comment

Related MCP Connectors

Related MCP Servers

  • books-catalog

    cggazca
    A
    license
    Not graded
    quality
    C
    maintenance
    A well-documented MCP server that exposes a local SQLite catalog of public-domain books through tools like search, get, filter by genre, top-rated, and catalog stats.
    MIT

  • opds-mcp

    pastukhov
    A
    license
    A
    quality
    B
    maintenance
    An MCP server that lets an LLM browse, search, and download books from OPDS catalogs (e.g., Project Gutenberg, Standard Ebooks) using tools for feed navigation, full-text search, and acquisition link downloads.
    4
    1
    AGPL 3.0

  • library-mcp

    forgemeshlabs
    A
    license
    A
    quality
    A
    maintenance
    This MCP server enables AI agents to search and retrieve exact, cited passages from a large corpus of public-domain books, including full-text search, book metadata, chapters, quotes, and 'ask book' Q&A. Payments are handled via x402 micropayments on Base.
    16
    8
    192
    MIT
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