Skip to main content
Glama

Wordnik

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

Schema Changelog

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

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "key": "user_research_topic"
+  },
+  {}
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint. Description adds scoping by identifier and behavior when key is omitted. No contradictions.

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?

Four sentences, front-loaded with purpose, then usage context, scoping, and companion tools. No redundant information.

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 one optional param, no output schema, and strong annotations, the description is complete: it explains purpose, when to use, parameter behavior, scoping, and related tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3. Description adds meaning by explaining that omitting the key lists all keys, and that the key retrieves a stored value, going beyond the schema's brief description.

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 retrieves a value via 'remember' or lists all keys if omitted. It uses specific verbs ('retrieve', 'list') and distinguishes from sibling tools 'remember' and 'forget'.

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?

Explicitly says to use it for looking up context without re-deriving, and pairs with remember/forget. No explicit alternatives, but context is clear for this retrieval tool.

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

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

B3.1/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, especially between Wordnik and Pipeworx domains. However, some overlap exists among data query tools (e.g., ask_pipeworx vs deep_research) and company lookups (entity_profile vs compare_entities), but descriptions are detailed enough to differentiate them in most cases.

Naming Consistency3/5

Naming conventions are mixed: some tools use snake_case (ai_visibility_check), others use descriptive phrases (ask_pipeworx_grounded), and some are single words (remember, recall). There is no uniform verb_noun pattern, though groups like polymarket_* and scan_* provide some consistency within their subsets.

Tool Count2/5

With 42 tools, the server is overloaded. It combines two distinct services (Wordnik dictionary and Pipeworx data) into one set, making it feel like two servers merged. Many tools are niche (e.g., hyphenation, random_words), increasing count without clear benefit. A split would improve coherence.

Completeness4/5

The Wordnik coverage is thorough (definitions, examples, pronunciation, frequency, etc.), and Pipeworx covers a wide range of data sources with tools for basic lookups, comparisons, research, and subscriptions. Minor gaps exist (e.g., no update/delete for Wordnik data), but overall the surface is comprehensive for the intended use.

Resources