Skip to main content
Glama

uooks

by io.github.pipeworx-io

Get Author

get_author
Read-onlyIdempotent

Fetch an author's profile from Open Library by their author key (e.g., 'OL23919A'). Returns name, birth_date, death_date, biographical summary, and Wikipedia URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
author_keyYesOpen Library author key (e.g., OL23919A)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bioYesBiographical summary
nameYesAuthor name
birth_dateYesBirth date if available
death_dateYesDeath date if available
wikipedia_urlYesWikipedia URL 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: +[
+  {
+    "author_key": "OL23919A"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "bio": {
+      "description": "Biographical summary",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "birth_date": {
+      "description": "Birth date if available",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "death_date": {
+      "description": "Death date if available",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "Author name",
+      "type": "string"
+    },
+    "wikipedia_url": {
+      "description": "Wikipedia URL if available",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "name",
+    "birth_date",
+    "death_date",
+    "bio",
+    "wikipedia_url"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "author_id": "2190855"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "affiliations": {
-      "description": "Author affiliations",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "author_id": {
-      "description": "Semantic Scholar author ID",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "citation_count": {
-      "description": "Total number of citations",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "h_index": {
-      "description": "H-index of the author",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "homepage": {
-      "description": "Author homepage URL",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "name": {
-      "description": "Author name",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "paper_count": {
-      "description": "Total number of papers published",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "papers": {
-      "description": "Recent publications (up to 20)",
-      "items": {
-        "properties": {
-          "citation_count": {
-            "description": "Number of citations for this paper",
-            "type": [
-              "number",
-              "null"
-            ]
-          },
-          "paper_id": {
-            "description": "Paper ID",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "title": {
-            "description": "Paper title",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "year": {
-            "description": "Publication year",
-            "type": [
-              "number",
-              "null"
-            ]
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "url": {
-      "description": "URL to author profile",
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "affiliations": {
+      "description": "Author affiliations",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "author_id": {
+      "description": "Semantic Scholar author ID",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "citation_count": {
+      "description": "Total number of citations",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "h_index": {
+      "description": "H-index of the author",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "homepage": {
+      "description": "Author homepage URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "Author name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "paper_count": {
+      "description": "Total number of papers published",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "papers": {
+      "description": "Recent publications (up to 20)",
+      "items": {
+        "properties": {
+          "citation_count": {
+            "description": "Number of citations for this paper",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "paper_id": {
+            "description": "Paper ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Paper title",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "year": {
+            "description": "Publication year",
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "url": {
+      "description": "URL to author profile",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "author_id": "2190855"
+  }
+]
  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 readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds value by listing the specific return fields (name, birth_date, death_date, biographical summary, Wikipedia URL), which is useful behavioral context beyond the annotations.

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, well-structured sentence that immediately states the purpose, input, and expected outputs. No wasted words or redundant information, making it highly scannable for an agent.

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 tool has one simple parameter, full schema coverage, and an output schema exists. The description notes the return fields, and the annotations supply safety semantics. Together, these provide complete context for an agent to select and 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?

Schema description coverage is 100% with the property description 'Open Library author key (e.g., OL23919A)' already including an example. The tool description repeats the example ('OL23919A') but adds no new semantic meaning beyond what the schema provides, so the baseline score 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 uses a specific verb ('Fetch') and clearly identifies the resource ('author's profile from Open Library') and the required input ('author key'). It distinguishes itself from sibling tools like get_book and get_book_work by focusing on the author entity.

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 context on when to use the tool: when you have an author key and need profile data. It does not explicitly mention alternatives or exclusions, but the example author key reinforces the usage scenario. A minor gap is the lack of explicit guidance on when not to use it (e.g., for book lookups).

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