Skip to main content
Glama

Librivox

by io.github.pipeworx-io

Audiobook

audiobook
Read-onlyIdempotent

Single audiobook by id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoAudiobook ID
titleNoAudiobook title
authorsNoList of authors
languageNoLanguage of audiobook
cover_urlNoCover image URL
narratorsNoList of narrators
totaltimeNoTotal duration in seconds
date_addedNoDate added to LibriVox
descriptionNoAudiobook description
url_iarchiveNoInternet Archive URL
url_librivoxNoLibriVox page URL
project_gutenberg_idNoProject Gutenberg ID if available

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": 1234
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "authors": {
+      "description": "List of authors",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Author ID",
+            "type": "number"
+          },
+          "name": {
+            "description": "Author name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "cover_url": {
+      "description": "Cover image URL",
+      "type": "string"
+    },
+    "date_added": {
+      "description": "Date added to LibriVox",
+      "type": "string"
+    },
+    "description": {
+      "description": "Audiobook description",
+      "type": "string"
+    },
+    "id": {
+      "description": "Audiobook ID",
+      "type": "number"
+    },
+    "language": {
+      "description": "Language of audiobook",
+      "type": "string"
+    },
+    "narrators": {
+      "description": "List of narrators",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Narrator ID",
+            "type": "number"
+          },
+          "name": {
+            "description": "Narrator name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "project_gutenberg_id": {
+      "description": "Project Gutenberg ID if available",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "title": {
+      "description": "Audiobook title",
+      "type": "string"
+    },
+    "totaltime": {
+      "description": "Total duration in seconds",
+      "type": "number"
+    },
+    "url_iarchive": {
+      "description": "Internet Archive URL",
+      "type": "string"
+    },
+    "url_librivox": {
+      "description": "LibriVox page URL",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe read operation. The description adds no additional behavioral context beyond the fact that it operates by ID, which is already captured in the schema.

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, short phrase that is concise and front-loaded. It contains no wasted words and effectively communicates the tool's scope for a simple lookup operation.

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 (one required ID param), rich annotations, and the presence of an output schema, the description adequately covers core functionality. It does not discuss error cases or return details, but those are likely covered by the output schema and the straightforward nature of the operation.

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 has a single 'id' parameter with no description. The description mentions 'by id', providing the semantic meaning that this is an audiobook identifier, which partially compensates for the 0% schema description coverage. However, it does not elaborate on the parameter's format or constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource (audiobook) and specifies it returns a single item by ID, distinguishing it from the sibling 'audiobooks' (plural). However, it lacks an explicit verb like 'get' or 'fetch', making the operation slightly implicit.

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?

No explicit guidance is given on when to use this tool versus alternatives like 'audiobooks'. The singular/plural naming implies use when an ID is available, but the agent must infer this context without direct instruction.

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

All Librivox 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

A3.5/5.0
Disambiguation2/5

The set mixes several unrelated domains (LibriVox, Pipeworx data lookup, Polymarket betting, memory, subscriptions), and within those domains there is heavy overlap: ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded/deep_research all route to the same 5,798 tools, and polymarket_edges/polymarket_arbitrage/polymarket_edge_tracker/polymarket_fill_risk/bet_research all scan prediction-market opportunities. An agent can easily pick the wrong tool when the same question fits several of them.

Naming Consistency3/5

Names are mostly lowercase snake_case, but the patterns are inconsistent across domains: some are verb-first (ask_pipeworx, compare_entities, generate_llms_txt), some are noun-first (audiobook, tracks, polymarket_edges), and pluralization varies (audiobook vs audiobooks, authors vs tracks). The Pipeworx family is internally consistent, but the overall set has no unified convention.

Tool Count2/5

35 tools is heavy for a server named Librivox, and only 4 of them (audiobook, audiobooks, authors, tracks) actually relate to LibriVox. The remaining ~31 tools (Pipeworx, Polymarket, memory, subscriptions, AI visibility) make the count far exceed what the server name and apparent purpose suggest.

Completeness2/5

For a LibriVox-focused server, the tool surface is thin: search and fetch audiobooks, search authors, and list tracks, but no browse by genre, no reader/search-by-reader, no language filter, no author detail endpoint. The Pipeworx side is quite comprehensive, but it does not make up for the gap relative to the server's stated identity.

Resources