Skip to main content
Glama

Quotable

by io.github.pipeworx-io

Search Quotes

search_quotes
Read-onlyIdempotent

Search quotes by keyword or phrase. Returns matching quotes with author names and topic tags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results per page (1–100, default 20; rounded up to 10/25/50/100)
queryYesKeyword or phrase to search for in quote content

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYesCurrent page number
countYesQuotes returned on this page
totalYesTotal matching quotes across all pages
quotesYesMatching quotes from search
total_pagesYesTotal number of pages

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 results per page (1–150, default 20)"New value: +"Number of results per page (1–100, default 20; rounded up to 10/25/50/100)"
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "success"
+  },
+  {
+    "limit": 10,
+    "query": "life and love"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Quotes returned on this page",
+      "type": "number"
+    },
+    "page": {
+      "description": "Current page number",
+      "type": "number"
+    },
+    "quotes": {
+      "description": "Matching quotes from search",
+      "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"
+    },
+    "total": {
+      "description": "Total matching quotes across all pages",
+      "type": "number"
+    },
+    "total_pages": {
+      "description": "Total number of pages",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "count",
+    "page",
+    "total_pages",
+    "quotes"
+  ],
+  "type": "object"
+}
  3. Added
  4. Removed
  5. First observed

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds no additional behavioral context such as rate limits, permission requirements, or search quirks; it merely restates the return of matching quotes, which is already implied by the tool's purpose.

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 exactly two sentences, front-loaded with the action 'Search quotes by keyword or phrase,' and contains no redundant or superfluous words. It is efficiently structured and immediately informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple search tool with a well-documented schema and annotations, the description is minimally adequate but lacks any usage context or mention of pagination or the limit's rounding behavior. The output schema likely covers return values, but the description could still note when to choose this tool over alternatives.

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% with both 'query' and 'limit' described in detail, including the bucketing behavior for limit. The description's 'keyword or phrase' adds no additional meaning beyond what the schema already provides, so a 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 clearly states the tool's purpose: 'Search quotes by keyword or phrase' with a specific verb and resource. It also specifies what is returned ('matching quotes with author names and topic tags'), distinguishing it from siblings like random_quote and get_authors.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It only states the operation without any exclusions, prerequisites, or named alternatives such as random_quote or search_within.

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