Skip to main content
Glama

Words Autocomplete

words_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").

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prefix": "hel"
    },
    "name": "words_autocomplete"
  }
}

Input Schema

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

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context by naming the Datamuse suggestion endpoint and saying results are ranked by score. It does not mention rate limits, authentication, or error behavior, so it adds only moderate value beyond the annotations.

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 tight sentences with the core operation front-loaded. The parenthetical examples clarify behavior without bloating the text. Every sentence contributes to understanding the tool.

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?

For a simple two-parameter lookup tool with a complete schema, full annotation coverage, and an output schema, the description is nearly complete. The main missing piece is sibling differentiation, but return values and parameter details are already handled by structured fields.

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 both the prefix and limit parameters are already documented in the schema. The description restates the prefix example but adds no new semantics for the limit parameter or any format details beyond what the schema provides. This is the expected baseline when the schema does the heavy lifting.

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 states a specific verb and resource: return word completions for a prefix via the Datamuse suggestion endpoint. It gives examples of input and output, so the agent can understand the operation clearly. It does not distinguish this from sibling tools such as find_words or find_synonyms, which keeps it below a 5.

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 explains what the tool does but gives no explicit guidance on when to use it instead of alternatives. With siblings like find_words and find_synonyms present, an agent could reasonably wonder which tool to choose. Usage is only implied by the word 'autocomplete' and the prefix example.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.