Skip to main content
Glama

uooks

by io.github.pipeworx-io

Get Book

get_book
Read-onlyIdempotent

Fetch Open Library edition details for a book by ISBN-10 or ISBN-13. Returns title, publish_date, number_of_pages, subjects (up to 10), description, cover_url, and author_keys for follow-up get_author calls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
isbnYesISBN-10 or ISBN-13

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesBook title
subjectsYesUp to 10 subject tags
cover_urlYesCover image URL
author_keysYesOpen Library author keys
descriptionYesBook description or summary
publish_dateYesPublication date
number_of_pagesYesNumber of pages

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: +[
+  {
+    "isbn": "9780451524935"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "author_keys": {
+      "description": "Open Library author keys",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "cover_url": {
+      "description": "Cover image URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "description": {
+      "description": "Book description or summary",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "number_of_pages": {
+      "description": "Number of pages",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "publish_date": {
+      "description": "Publication date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "subjects": {
+      "description": "Up to 10 subject tags",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "title": {
+      "description": "Book title",
+      "type": "string"
+    }
+  },
+  "required": [
+    "title",
+    "publish_date",
+    "number_of_pages",
+    "subjects",
+    "description",
+    "cover_url",
+    "author_keys"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "id": 1342
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "authors": {
-      "description": "List of book authors",
-      "items": {
-        "properties": {
-          "birth_year": {
-            "description": "Author birth year or null",
-            "type": [
-              "number",
-              "null"
-            ]
-          },
-          "death_year": {
-            "description": "Author death year or null",
-            "type": [
-              "number",
-              "null"
-            ]
-          },
-          "name": {
-            "description": "Author name",
-            "type": "string"
-          }
-        },
-        "required": [
-          "name",
-          "birth_year",
-          "death_year"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "download_count": {
-      "description": "Number of downloads",
-      "type": "number"
-    },
-    "formats": {
-      "additionalProperties": {
-        "type": "string"
-      },
-      "description": "Available download formats and URLs",
-      "type": "object"
-    },
-    "id": {
-      "description": "Project Gutenberg book ID",
-      "type": "number"
-    },
-    "languages": {
-      "description": "Languages the book is available in",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "subjects": {
-      "description": "Subject tags for the book",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "title": {
-      "description": "Book title",
-      "type": "string"
-    }
-  },
-  "required": [
-    "id",
-    "title",
-    "authors",
-    "languages",
-    "subjects",
-    "download_count",
-    "formats"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "authors": {
+      "description": "List of book authors",
+      "items": {
+        "properties": {
+          "birth_year": {
+            "description": "Author birth year or null",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "death_year": {
+            "description": "Author death year or null",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Author name",
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "birth_year",
+          "death_year"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "download_count": {
+      "description": "Number of downloads",
+      "type": "number"
+    },
+    "formats": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "description": "Available download formats and URLs",
+      "type": "object"
+    },
+    "id": {
+      "description": "Project Gutenberg book ID",
+      "type": "number"
+    },
+    "languages": {
+      "description": "Languages the book is available in",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "subjects": {
+      "description": "Subject tags for the book",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "title": {
+      "description": "Book title",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "title",
+    "authors",
+    "languages",
+    "subjects",
+    "download_count",
+    "formats"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": 1342
+  }
+]
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior. The description adds transparency about the specific returned fields, the 'subjects (up to 10)' limit, and the chaining opportunity to get_author, which goes beyond the structured annotations and provides useful behavioral context.

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?

Two sentences, front-loaded with purpose, and every clause adds value: the lookup method, the input format, the returned fields, and a follow-up hint. No filler or redundancy.

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 simple single-parameter fetch tool with strong annotations and an output schema, the description is complete. It states the input condition, the output highlights, and a relevant follow-up. Nothing essential 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?

Schema coverage is 100%, and the single parameter 'isbn' is already described as 'ISBN-10 or ISBN-13'. The description repeats this without adding new format constraints, validation rules, or edge-case guidance, so it adds minimal value beyond the schema.

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 a specific verb ('Fetch'), a specific resource ('Open Library edition details'), and the exact lookup key (ISBN-10 or ISBN-13). It differentiates from siblings like get_book_work (edition vs. work) and search_books (fetch by identifier vs. search) by specifying the input and the returned fields.

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 tool when you have an ISBN and need edition-level metadata. It does not explicitly name alternatives or exclusion criteria, but the ISBN-focused scope strongly implies when it should be used. Mentioning author_keys for follow-up get_author calls adds practical guidance.

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

All uooks 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.1/5.0
Disambiguation3/5

Several tool families overlap at the boundaries: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route questions to the same 5,724 tools, and ask_pipeworx_beta is currently functionally identical to ask_pipeworx. The Polymarket family is large but each member has a fairly distinct role (research vs. edge scan vs. fill risk vs. tracking); the memory trio and book tools are clear.

Naming Consistency3/5

Most tools follow a snake_case verb_noun pattern (get_book, create, search_books, resolve_entity, list_subscriptions), but there are notable exceptions: recall/remember/forget are bare verbs without a domain prefix, ask_pipeworx begins with a verb but doesn't follow the noun-object structure, and ai_visibility_check/generate_llms_txt break the pattern. It's readable and mostly predictable, but not uniform.

Tool Count3/5

35 tools is heavy and exceeds the typical well-scoped range, but the server is a meta-platform exposing a universal data router plus prediction-market analysis, book lookup, memory, subscriptions, and several composite research tools. Each tool appears to earn its place, though the set feels sprawling and would benefit from consolidation of the ask_pipeworx variants.

Completeness4/5

Coverage is thorough within the apparent domains: data lookup has multiple tiers (casual, grounded, deep research, claim validation), the Polymarket workflow is complete from research to edge discovery to fill-risk verification, memory has save/retrieve/delete, and subscriptions have create/list/cancel/pull. Minor gaps exist (e.g., book author search by name only via Open Library key, no direct tool for invoking a specific raw data pack), but nothing that would strand an agent.

Resources