Skip to main content
Glama

Dengdeng Chinese Dictionary

Look up a Chinese word

look_up_word
Read-onlyIdempotent

Look up one Chinese word or character in the Dengdeng Chinese–English dictionary. Returns the simplified and traditional forms, tone-marked pinyin for each reading, the English meanings, the HSK 3.0 band, measure words, and, when the word has them, two example sentences with pinyin and English, an audio URL and a short cartoon. Also returns the URL of the word's dictionary page and links to its sections: the cartoon, stroke order, example sentences and, for some words, a slang, idiom or measure-word guide. Use it for questions such as “what does 加油 mean” or “how do you pronounce 银行”. The word must be written in Chinese characters; use search_dictionary for pinyin or English. It looks up dictionary entries only and does not translate sentences.

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": "look_up_word"
  }
}

Input Schema

NameRequiredDescriptionDefault
wordYesOne Chinese word or character in simplified or traditional characters, for example 你好 or 學習.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by enumerating the returned fields (simplified/traditional forms, pinyin per reading, HSK band, measure words, examples, audio URL, cartoon) and by stating the scope boundary that it looks up entries only and does not translate sentences. It stops short of mentioning rate limits or failure behavior for unknown words, which keeps it from a 5.

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?

Front-loaded with the core action, then returns, then usage and exclusions in a logical order. The return-value enumeration is long but each item is informative; a slightly tighter phrasing of the link list would earn a 5.

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?

There is no output schema, so the description carries the burden of describing return values, and it does so thoroughly, including optional fields ("when the word has them") and the page/section URLs. Combined with the input constraint and the sibling routing, an agent has everything needed to call it correctly.

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%, so the baseline is 3, but the description adds meaning the schema does not: the word must be written in Chinese characters and pinyin or English input belongs to a different tool. That is a genuine disambiguation constraint rather than a restatement of the schema's simplified/traditional note.

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?

States a specific verb and resource ("Look up one Chinese word or character in the Dengdeng Chinese–English dictionary") and immediately scopes it to a single word, which separates it from the sibling search_dictionary. An agent can tell exactly what this returns 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 Guidelines5/5

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

Gives concrete use-case examples ("what does 加油 mean", "how do you pronounce 银行"), an explicit input constraint (must be Chinese characters), a named alternative for the other case ("use search_dictionary for pinyin or English"), and an explicit exclusion ("does not translate sentences"). When-to-use, when-not-to-use, and the alternative are all present.

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.

Resources