Quotable

Get Authors

get_authors

Read-onlyIdempotent

Look up an author by slug (e.g., "albert-einstein"). Returns bio, description, and total quote count. Without a slug, returns a page of the author list — the upstream list is unordered and cannot be searched, so prefer passing a slug.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	No	Author slug(s) to look up, e.g. "albert-einstein". Supports pipe-separated values for multiple authors.
`limit`	No	Authors per page when browsing without a slug (1–100, default 20; rounded up to 10/25/50/100)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No
`authors`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 19, 2026

addedOutput schema / properties / authors

Added value: +{
+  "items": {
+    "properties": {
+      "bio": {
+        "type": "string"
+      },
+      "description": {
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "quote_count": {
+        "type": "number"
+      },
+      "slug": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / count
```
Added value: +{
+  "type": "number"
+}
```

removedOutput schema / properties / hint

Removed value: -{
-  "type": "string"
-}

removedOutput schema / properties / message

Removed value: -{
-  "type": "string"
-}

removedOutput schema / properties / ok

Removed value: -{
-  "type": "boolean"
-}

removedOutput schema / properties / op

Removed value: -{
-  "type": "string"
-}

removedOutput schema / properties / reason

Removed value: -{
-  "type": "string"
-}

removedOutput schema / properties / upstream_status
```
Removed value: -{
-  "type": "number"
-}
```

Changed1 schema field changedJul 31, 2026

changedInput schema / properties / limit / description

Previous value: -"Number of authors to return (1–150, default 20)"New value: +"Authors per page when browsing without a slug (1–100, default 20; rounded up to 10/25/50/100)"

Changed10 schema fields changedJun 2, 2026

removedOutput schema / properties / authors

Removed value: -{
-  "description": "Author records",
-  "items": {
-    "properties": {
-      "bio": {
-        "description": "Short biography",
-        "type": "string"
-      },
-      "description": {
-        "description": "Detailed description",
-        "type": "string"
-      },
-      "id": {
-        "description": "Author unique identifier",
-        "type": "string"
-      },
-      "link": {
-        "description": "URL link to author",
-        "type": "string"
-      },
-      "name": {
-        "description": "Full author name",
-        "type": "string"
-      },
-      "quote_count": {
-        "description": "Total quotes by this author",
-        "type": "number"
-      },
-      "slug": {
-        "description": "Author slug for filtering",
-        "type": "string"
-      }
-    },
-    "required": [
-      "id",
-      "name",
-      "slug",
-      "bio",
-      "description",
-      "quote_count",
-      "link"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / properties / count

Removed value: -{
-  "description": "Authors returned",
-  "type": "number"
-}

addedOutput schema / properties / hint
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / message
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / ok
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / op
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / reason
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / total

Removed value: -{
-  "description": "Total matching authors across all pages",
-  "type": "number"
-}

addedOutput schema / properties / upstream_status
```
Added value: +{
+  "type": "number"
+}
```

removedOutput schema / required

Removed value: -[
-  "total",
-  "count",
-  "authors"
-]

AddedMay 13, 2026
RemovedApr 27, 2026
First observedApr 22, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond those annotations: the upstream list is unordered, cannot be searched, and the no-slug path returns a page rather than a complete list.

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 focused sentences: the first states the primary lookup behavior and return fields, the second explains the fallback list behavior and the preference for slugs. Every sentence earns its place, with no redundant filler.

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 tool with two optional parametershol, an output schema present, and read-only annotations, the description covers the core lookup, the fallback pagination, the ordering limitation, and the recommended invocation style. Nothing critical is missing for an agent to call it 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 both slug and limit already documented with examples and constraints, so the description does not need to compensate. It adds context about the no-slug pagination behavior, but the schema already carries most of the parameter meaning.

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 opens with a specific verb and resource: 'Look up an author by slug.' It also distinguishes the tool from pure search/list tools by explaining that without a slug it returns an unordered, non-searchable page of authors, making the author-lookup purpose clear.

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: pass a slug for a lookup, and without a slug you get a paginated list. It explicitly warns that the upstream list is unordered and cannot be searched, and advises preferring a slug, but it does not name an alternative sibling tool or specify when to choose this tool over related search tools.

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

All Quotable tools Inspect

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.