Skip to main content
Glama

words

by io.github.pipeworx-io

Autocomplete

autocomplete
Read-onlyIdempotent

Return word completions for a given prefix string using the Datamuse suggestion endpoint. Takes a prefix (e.g., "hel") and returns matching words ranked by score (e.g., "hello", "help", "helpless").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return (default: 10)
prefixYesThe prefix to autocomplete (e.g. "hel" returns "hello", "help", etc.)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
prefixYesThe prefix that was autocompleted
resultsYesList of word completions ranked by score

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: +[
+  {
+    "prefix": "hel"
+  },
+  {
+    "limit": 12,
+    "prefix": "inter"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "prefix": {
+      "description": "The prefix that was autocompleted",
+      "type": "string"
+    },
+    "results": {
+      "description": "List of word completions ranked by score",
+      "items": {
+        "properties": {
+          "score": {
+            "description": "Completion relevance score",
+            "type": "number"
+          },
+          "word": {
+            "description": "The completed word",
+            "type": "string"
+          }
+        },
+        "required": [
+          "word",
+          "score"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "prefix",
+    "results"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "prefix": "hel"
-  },
-  {
-    "limit": 12,
-    "prefix": "inter"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "prefix": {
-      "description": "The prefix that was autocompleted",
-      "type": "string"
-    },
-    "results": {
-      "description": "List of word completions ranked by score",
-      "items": {
-        "properties": {
-          "score": {
-            "description": "Completion relevance score",
-            "type": "number"
-          },
-          "word": {
-            "description": "The completed word",
-            "type": "string"
-          }
-        },
-        "required": [
-          "word",
-          "score"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "prefix",
-    "results"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "prefix": {
+      "description": "The prefix that was autocompleted",
+      "type": "string"
+    },
+    "results": {
+      "description": "List of word completions ranked by score",
+      "items": {
+        "properties": {
+          "score": {
+            "description": "Completion relevance score",
+            "type": "number"
+          },
+          "word": {
+            "description": "The completed word",
+            "type": "string"
+          }
+        },
+        "required": [
+          "word",
+          "score"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "prefix",
+    "results"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "prefix": "hel"
+  },
+  {
+    "limit": 12,
+    "prefix": "inter"
+  }
+]
  5. First observed

TDQS

A4/5.0
Behavior4/5

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

The description adds context beyond annotations by naming the Datamuse suggestion endpoint and explaining that results are 'ranked by score'. While annotations already declare readOnlyHint and idempotentHint, the description enriches understanding of the data source and output ordering without repeating annotation details.

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, with the verb and resource front-loaded. It includes a concrete example, and every sentence adds value with no fluff. Perfectly concise and well-structured.

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 (2 params, output schema present, strong annotations), the description adequately covers what the tool does and how it behaves. It could mention overlap with sibling tools, but the description is sufficient for a straightforward autocomplete operation.

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%, so the schema already documents both prefix and limit parameters with descriptions and examples. The tool description does not add significant extra meaning beyond the schema's own examples, hence 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 function: 'Return word completions for a given prefix string' using the Datamuse suggestion endpoint. It provides specific examples ('hel' returns 'hello', 'help') that illustrate the behavior and distinguish it from sibling tools like find_synonyms or find_rhymes.

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

Usage Guidelines3/5

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

The description implies usage by showing a prefix example, but it does not explicitly state when to prefer this tool over alternatives such as find_words or explore for related terms. There is no mention of when not to use it, leaving room for ambiguity.

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

All words 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

Several tools overlap heavily: ask_pipeworx_beta is currently identical to ask_pipeworx, and find_related with syn/rhy options duplicates find_synonyms and find_rhymes. The six Polymarket tools and four entity-research tools also have fuzzy boundaries, so agents will struggle to reliably pick the right one.

Naming Consistency2/5

Conventions are mixed: most tools follow verb_noun (ask_, find_, compare_, validate_) but several are bare nouns or noun phrases (entity_profile, recent_alertes, recent_changes) and others are bare verbs (remember, forget, subscribe, unsubscribe). The server name 'words' matches only five of 36 tools, adding further confusion about what to expect here.

Tool Count2/5

36 tools is well into the heavy range, and the set bundles word lookups, a universal data router, six Polymarket tools, memory, subscriptions, and meta-utilities under one server. Many of these would be better split into dedicated, purpose-scoped servers.

Completeness4/5

For the dominant data-research and prediction-market scope, the surface is strong: grounded lookups, deep reseach, entity profiles, compareions, change feeds, claim verification, edge scanners, fill-risk checks, subscriptions, and memory are all covered. Minor gaps exist: taking 'words' literally there is no defintion or spelling tool, and there is no generic open-web search, but as a data-research toolkit it is quite complete.

Resources