Skip to main content
Glama

Wordnik

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Examples

examples
Read-onlyIdempotent

Usage examples.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNo
wordYes
limitNo
useCanonicalNo
includeDuplicatesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
examplesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / count
      Removed value: -{
-  "description": "Number of items returned.",
-  "type": "integer"
-}
    • addedOutput schema / properties / examples
      Added value: +{
+  "items": {
+    "properties": {
+      "author": {
+        "type": "string"
+      },
+      "documentId": {
+        "type": "number"
+      },
+      "exampleId": {
+        "type": "number"
+      },
+      "provider": {
+        "properties": {
+          "id": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "rating": {
+        "type": "number"
+      },
+      "text": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      },
+      "word": {
+        "type": "string"
+      },
+      "year": {
+        "type": "number"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedOutput schema / properties / items
      Removed value: -{
-  "items": {
-    "properties": {
-      "id": {
-        "description": "Example ID",
-        "type": "number"
-      },
-      "text": {
-        "description": "Example text",
-        "type": "string"
-      },
-      "title": {
-        "description": "Example source title",
-        "type": "string"
-      },
-      "url": {
-        "description": "Source URL",
-        "type": "string"
-      },
-      "year": {
-        "description": "Year of example",
-        "type": "number"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}
    • removedOutput schema / required
      Removed value: -[
-  "items",
-  "count"
-]
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "word": "eloquent"
+  },
+  {
+    "limit": 3,
+    "skip": 0,
+    "word": "paradigm"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Example ID",
+            "type": "number"
+          },
+          "text": {
+            "description": "Example text",
+            "type": "string"
+          },
+          "title": {
+            "description": "Example source title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Source URL",
+            "type": "string"
+          },
+          "year": {
+            "description": "Year of example",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

D1.8/5.0
Behavior2/5

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

The description contributes no behavioral context beyond what annotations already state. The readOnly, openWorld, idempotent, and non-destructive hints are present in annotations, but the description does not disclose anything about pagination behavior, canonicalization, duplicate handling, or response semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

'Usage examples.' is extremely concise, but this is under-specification rather than effective conciseness. It front-loads little of value and contains no structured information that helps an agent call the tool.

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

Completeness1/5

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

For a tool with five parameters, no schema descriptions, an output schema, and many dictionary-related sibling tools, the description is far too incomplete. An agent cannot determine what the tool returns, how to construct a valid request, or when it is the right choice.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no meaning to any of the five parameters. The schema's example invocations hint at 'word', 'skip', and 'limit', but parameters like 'useCanonical' and 'includeDuplicates' are completely unexplained, and the description does not compensate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Usage examples.' is a noun phrase that restates the tool name and title without a clear verb or resource. It does not specify that these are usage examples for a word, nor does it distinguish this tool from siblings like 'top_example' or 'definitions'.

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?

No guidance is provided about when to use this tool versus alternatives. The description mentions neither the required 'word' parameter nor any relationship to sibling tools such as 'definitions', 'phrases', or 'top_example'.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources