Skip to main content
Glama

AutoTasker Hub — China Social Data API

define_word

English dictionary entry with definitions and phonetics. $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": "define_word"
  }
}

Input Schema

NameRequiredDescriptionDefault
wordYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are provided, so the description bears the full burden. It partly covers this: 'definitions and phonetics' names the returned content, and '$0.01 USDC' discloses the paid, metered per-call nature of the tool, which is not in structured fields and matters for invocation. It does not state whether the call fails on unknown words, whether authentication or a wallet balance is required, or what an empty result looks like. The paid-call disclosure is real beyond-schema value, so this is stronger than a bare minimum, but not complete.

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 short clauses cover the return content and the cost with no filler. The cost sentence is short and separated, so it is front-loaded enough not to bury the purpose.

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?

The schema is trivial and there are no annotations, so completeness depends on the description. A paid, unannotated lookup tool should state whether one word per call and what an unknown word returns. Covering cost is good, but the input contract and failure mode are missing.

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 the single required 'word' parameter is undocumented in the schema and the description does not compensate. It implies English-only input and does not specify whether inflected forms are accepted. This is near the minimum for one undocumented parameter and falls short of a 3 because it adds almost no meaning beyond the schema.

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 states a specific resource (an English dictionary entry) and what it returns (definitions and phonetics). Unlike siblings that search documents or fetch facts, its purpose is lookup of word meaning, so an agent can choose it over datamuse_synonyms or other resource tools without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when the tool applies by naming 'English dictionary entry', which suggests lookup of a single English word. It gives no condition for when to avoid it versus siblings such as datamuse_synonyms, and says nothing about inputs that fail, for example non-English terms. Usage is inferable but not stated.

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.