Skip to main content
Glama

Quotable

by io.github.pipeworx-io

Random Quote

random_quote
Read-onlyIdempotent

Get a random quote, optionally filtered by tag (e.g., "Wisdom", "Motivational") or author slug. Returns quote text, author, and tags. Tags come from a fixed list — call list_tags to see it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoFilter by tag(s) from list_tags. Comma for AND, pipe for OR, e.g. "Wisdom" or "Humorous|Science". Case is normalised for you.
limitNoNumber of quotes to return (1–10, default 1)
authorNoFilter by author slug, e.g. "albert-einstein"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed3 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "limit": 1
-  },
-  {
-    "author": "albert-einstein",
-    "limit": 5,
-    "tags": "wisdom"
-  }
-]New value: +[
+  {
+    "limit": 1
+  },
+  {
+    "author": "albert-einstein",
+    "limit": 5,
+    "tags": "Wisdom"
+  }
+]
    • changedInput schema / properties / limit / description
      Previous value: -"Number of quotes to return (1–50, default 1)"New value: +"Number of quotes to return (1–10, default 1)"
    • changedInput schema / properties / tags / description
      Previous value: -"Filter by tag(s). Use comma for AND, pipe for OR, e.g. \"wisdom\" or \"humor|science\""New value: +"Filter by tag(s) from list_tags. Comma for AND, pipe for OR, e.g. \"Wisdom\" or \"Humorous|Science\". Case is normalised for you."
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 1
+  },
+  {
+    "author": "albert-einstein",
+    "limit": 5,
+    "tags": "wisdom"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "oneOf": [
+    {
+      "properties": {
+        "author": {
+          "description": "Author name",
+          "type": "string"
+        },
+        "author_slug": {
+          "description": "Author slug for filtering",
+          "type": "string"
+        },
+        "content": {
+          "description": "Quote text",
+          "type": "string"
+        },
+        "id": {
+          "description": "Quote unique identifier",
+          "type": "string"
+        },
+        "length": {
+          "description": "Character count of quote",
+          "type": "number"
+        },
+        "tags": {
+          "description": "Topic tags for the quote",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "id",
+        "content",
+        "author",
+        "author_slug",
+        "length",
+        "tags"
+      ],
+      "type": "object"
+    },
+    {
+      "properties": {
+        "count": {
+          "description": "Number of quotes returned",
+          "type": "number"
+        },
+        "quotes": {
+          "description": "Array of random quotes",
+          "items": {
+            "properties": {
+              "author": {
+                "description": "Author name",
+                "type": "string"
+              },
+              "author_slug": {
+                "description": "Author slug for filtering",
+                "type": "string"
+              },
+              "content": {
+                "description": "Quote text",
+                "type": "string"
+              },
+              "id": {
+                "description": "Quote unique identifier",
+                "type": "string"
+              },
+              "length": {
+                "description": "Character count of quote",
+                "type": "number"
+              },
+              "tags": {
+                "description": "Topic tags for the quote",
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              }
+            },
+            "required": [
+              "id",
+              "content",
+              "author",
+              "author_slug",
+              "length",
+              "tags"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "count",
+        "quotes"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}
  3. Added
  4. Removed
  5. First observed

TDQS

A4/5.0
Behavior4/5

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

With annotations indicating read-only, idempotent, and non-destructive behavior, the description adds useful context: returns quote text, author, and tags, and tags come from a fixed list. This goes beyond annotations and clarifies the response shape and tag source. No contradiction found.

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 concise sentences that front-load the primary action, include filter examples, return contents, and a valuable tag-list tip. No redundant wording, every sentence earns its place.

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, the description covers the core purpose, optional filters, return contents, and the tag prerequisite. An output schema exists, so return details are not required. It could mention the default limit or the random nature per call, but the description is already sufficient for most use cases.

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 input schema already provides 100% coverage with descriptions for all three parameters. The description's mention of 'tag' and 'author slug' aligns with the schema but adds no new semantics. The fixed-list note is also present in the schema, so the description contributes minimal additional parameter meaning.

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 states the tool's function: 'Get a random quote' with optional filters by tag or author slug. It also mentions return contents (quote text, author, tags), making the purpose explicit. It doesn't explicitly differentiate from sibling search_quotes, but the random nature is 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 usage context: use when you want a random quote, optionally filtered. It also provides a direct pointer to list_tags as a prerequisite for tags, which is helpful. However, it doesn't explicitly mention when not to use this tool or alternatives like search_quotes, so it's not a full 5.

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

All Quotable 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.7/5.0
Disambiguation2/5

The ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) is highly overlapping—two of them are explicitly identical right now—and the six polymarket_* tools plus bet_research create unclear boundaries between prediction-market analysis tools. Company-focused tools (entity_profile, compare_entities, recent_changes, resolve_entity) also partially overlap in what they fetch, making tool selection error-prone.

Naming Consistency4/5

Most tool names follow a clear snake_case pattern with descriptive verbs (search_quotes, resolve_entity, validate_claim, subscribe, unsubscribe). There is good use of family prefixes like polymarket_* and pipeworx_*, though the Pipeworx family mixes prefix and suffix placement (ask_pipeworx vs. pipeworx_feedback), which is a minor inconsistency.

Tool Count2/5

35 tools is far too many for a server named 'Quotable', especially since only 4 tools (get_authors, list_tags, random_quote, search_quotes) relate to quotes. The rest span data lookup, prediction markets, memory, subscriptions, AI visibility, and dependency scanning—an extremely broad, unfocused scope that overwhelms the apparent purpose.

Completeness3/5

The quote-related surface is minimal but functional (random, search, authors, tags), though missing obvious operations like get_quote_by_id. The data-lookup and prediction-market domains are thoroughly covered with grounding, research, arbitrage, and fill-risk tools, so the broader set is complete—but it does not serve the server's stated identity as a quotes provider.

Resources