Skip to main content
Glama

Quotable

by io.github.pipeworx-io

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
NameRequiredDescriptionDefault
slugNoAuthor slug(s) to look up, e.g. "albert-einstein". Supports pipe-separated values for multiple authors.
limitNoAuthors per page when browsing without a slug (1–100, default 20; rounded up to 10/25/50/100)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
opNo
hintNo
reasonNo
messageNo
upstream_statusNo

Schema Changelog

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

  1. Changed1 schema field changed
    • 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)"
  2. Changed10 schema fields changed
    • 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"
-]
  3. Added
  4. Removed
  5. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The annotations already establish read-only, idempotent, and non-destructive characteristics. The description adds meaningful behavioral context: it returns 'bio, description, and total quote count,' and reveals that the list mode is unordered and cannot be searched—information not available from annotations alone.

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 two sentences long, front-loaded with the primary action, and every phrase earns its place—covering the lookup mode, the fallback list mode, and the critical limitation without 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?

Given the presence of an output schema and full parameter descriptions, the description rounds out the context by explaining the two usage modes and the list's unordered nature. This is sufficient for a read-only lookup tool; no missing prerequisites or error scenarios are critical.

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 schema descriptions fully cover both parameters (slug with pipe-separated support, limit with range and rounding), so the description adds limited semantic detail. The only extra is the usage recommendation to prefer slug, which is more about context than parameter meaning. Baseline 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 clearly states the tool's purpose: 'Look up an author by slug' and specifies the resource (authors) and the key (slug). It also distinguishes the list mode and notes the limitation ('upstream list is unordered and cannot be searched'), differentiating it from search-focused siblings like search_quotes.

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 direct usage guidance by instructing users to 'prefer passing a slug' and explaining that the list mode is unordered and non-searchable. This implies when to use slug versus list, though it does not explicitly name alternative tools or exclusion scenarios.

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