Skip to main content
Glama

AutoTasker Hub — China Social Data API

datamuse_synonyms

Synonyms and related words via Datamuse lexical DB. NLP helper. $0.01 USDC.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "word": "<word>"
    },
    "name": "datamuse_synonyms"
  }
}

Input Schema

NameRequiredDescriptionDefault
wordYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the data source and a $0.01 USDC cost, but omits read-only safety, rate limits, error behavior, and return format; for a simple lookup this is minimally adequate.

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

Conciseness4/5

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

The description is front-loaded and only three fragments long. 'NLP helper' is vague filler, but the cost disclosure earns its place, and there is no wasted prose.

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

Completeness2/5

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

For a lexical lookup with no annotations, no output schema, and 0% parameter documentation, the description is too thin. It should at least explain what 'limit' controls and what the response contains, neither of which is covered elsewhere.

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% for two parameters. The purpose implies that 'word' is the query term, but the 'limit' parameter (default 10, maximum 30) is never explained in the description, leaving half the schema undocumented.

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 clearly states the resource and data source: 'Synonyms and related words via Datamuse lexical DB.' An agent can tell it returns lexical relations, but there is no sibling differentiation or explicit verb, so it falls short of 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?

It offers no when-to-use guidance, no exclusions, and no alternatives. 'NLP helper' is vague and does not tell an agent whether to choose this over define_word or other lexical tools.

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.