Wordnik

Search

search

Read-onlyIdempotent

Search the Wordnik dictionary by query string with wildcard support; filter by part of speech, length, and corpus count. Returns matching word strings.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`skip`	No
`limit`	No
`query`	Yes
`maxLength`	No
`minLength`	No
`caseSensitive`	No
`minCorpusCount`	No
`minDictionaryCount`	No
`excludePartOfSpeech`	No
`includePartOfSpeech`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`totalResults`	No	Total number of results
`searchResults`	No	Search results

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 27, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "cat"
+  },
+  {
+    "limit": 20,
+    "minLength": 4,
+    "query": "^un"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "searchResults": {
+      "description": "Search results",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Result ID",
+            "type": "number"
+          },
+          "word": {
+            "description": "Matched word",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "totalResults": {
+      "description": "Total number of results",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. Description adds wildcard support and return type (word strings), but lacks details on pagination, rate limits, or result ordering.

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?

Two sentences, front-loaded with key action and result. No wasted words.

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?

Output schema exists, so return type is covered. However, with 10 parameters and 0% schema description coverage, the description should provide more detailed parameter guidance. Currently leaves many parameters undocumented.

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

Parameters2/5

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

Schema description coverage is 0%, so description must carry parameter meaning. It mentions filtering by part of speech, length, and corpus count but does not map to specific parameter names like includePartOfSpeech, minLength, minCorpusCount. Does not explain wildcard syntax or required query param.

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?

Describes tool as searching Wordnik dictionary with query string and wildcard support, and mentions filtering by part of speech, length, and corpus count. Clear verb and resource, but does not differentiate from sibling tools like search_within or deep_research.

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 explicit guidance on when to use this tool versus alternatives. Does not list exclusions or mention context such as query limitations.

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

All Wordnik tools Inspect

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.