Skip to main content
Glama

Librivox

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Tracks

tracks
Read-onlyIdempotent

LibriVox free public-domain audiobooks — the individual chapter tracks of one LibriVox recording project, given its project_id. Each track returns its section number, title, playtime, the volunteer reader who recorded it, file size and the direct MP3 URL. Answers which chapters are in a LibriVox audiobook and where to stream or download each one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / sections
      Added value: +{
+  "items": {
+    "properties": {
+      "file_name": {
+        "type": "null"
+      },
+      "id": {
+        "type": "string"
+      },
+      "language": {
+        "type": "string"
+      },
+      "listen_url": {
+        "type": "string"
+      },
+      "playtime": {
+        "type": "string"
+      },
+      "section_number": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedOutput schema / properties / tracks
      Removed value: -{
-  "description": "List of audio tracks for the audiobook",
-  "items": {
-    "properties": {
-      "date_recorded": {
-        "description": "Recording date",
-        "type": "string"
-      },
-      "length": {
-        "description": "Track length in seconds",
-        "type": "number"
-      },
-      "narrator": {
-        "description": "Narrator name",
-        "type": "string"
-      },
-      "title": {
-        "description": "Track title",
-        "type": "string"
-      },
-      "track_number": {
-        "description": "Track number",
-        "type": "number"
-      },
-      "url_m4b": {
-        "description": "M4B download URL",
-        "type": "string"
-      },
-      "url_mp3": {
-        "description": "MP3 download URL",
-        "type": "string"
-      },
-      "url_ogg": {
-        "description": "OGG download URL",
-        "type": "string"
-      },
-      "url_project": {
-        "description": "Project URL",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "project_id": 1234
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "tracks": {
+      "description": "List of audio tracks for the audiobook",
+      "items": {
+        "properties": {
+          "date_recorded": {
+            "description": "Recording date",
+            "type": "string"
+          },
+          "length": {
+            "description": "Track length in seconds",
+            "type": "number"
+          },
+          "narrator": {
+            "description": "Narrator name",
+            "type": "string"
+          },
+          "title": {
+            "description": "Track title",
+            "type": "string"
+          },
+          "track_number": {
+            "description": "Track number",
+            "type": "number"
+          },
+          "url_m4b": {
+            "description": "M4B download URL",
+            "type": "string"
+          },
+          "url_mp3": {
+            "description": "MP3 download URL",
+            "type": "string"
+          },
+          "url_ogg": {
+            "description": "OGG download URL",
+            "type": "string"
+          },
+          "url_project": {
+            "description": "Project URL",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful context about what is returned, including direct MP3 URLs and reader attribution, but does not discuss error cases or limits. This is adequate but not deeply behavior-rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core subject and remains fairly compact. The final sentence somewhat restates the second sentence, but it adds a practical user-oriented framing. Overall it is appropriately sized and readable.

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?

For a one-parameter, read-only, idempotent lookup with an output schema present, the description is complete. It names the required input, explains the project scope, and summarizes what each track contains. No essential calling information is missing.

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?

With schema description coverage at 0%, the description must compensate for project_id. It partially does by explaining that project_id refers to a LibriVox recording project. It does not explain where to find the ID or any format constraints, but the single-number parameter and example make this minimally sufficient.

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 is specific: it identifies the tool as returning the individual chapter tracks of a LibriVox project, given its project_id. It enumerates the returned fields (section number, title, playtime, reader, file size, MP3 URL) and clearly answers the use case of which chapters are in an audiobook. This distinguishes it from sibling tools like audiobook/audiobooks by focusing on chapter-level tracks.

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 gives clear context: use this when you need the chapter tracks for a specific LibriVox recording project and where to stream or download each one. It does not explicitly name alternatives or say when not to use it, but the chapter-level scope makes the intended use apparent.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources