Dengdeng Chinese Dictionary

HSK 3.0 word list

hsk_word_list

Read-onlyIdempotent

One page (100 words) of an HSK 3.0 vocabulary list (the 2021 standard, also called the new HSK), ordered by pinyin, with pinyin, a short English meaning and the word page URL for each word. Bands 1–6 are separate lists; 7-9 is the combined advanced band. Returns the number of pages, so ask for later pages with the page argument. To find the band of one word, use look_up_word or search_dictionary instead of scanning the lists.

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": {
      "band": "<band>"
    },
    "name": "hsk_word_list"
  }
}

Input Schema

Name	Required	Description	Default
`band`	Yes	The HSK 3.0 band: 1, 2, 3, 4, 5, 6 or 7-9.
`page`	No	The page of the list, 100 words per page. The first page is 1.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real context: fixed 100-word page size, pinyin ordering, the fields returned per word, and that the response reports the total page count. It does not discuss rate limits or failure modes, but nothing essential is missing.

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?

Three sentences, each carrying distinct information: what is returned, how bands and paging work, and when to use a sibling instead. Front-loaded with the resource and no filler.

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?

For a two-parameter read-only list tool with no output schema, the description covers return contents, page size, total page count, and band semantics. An agent has everything needed to call it correctly on the first try.

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 baseline is 3. The description goes beyond the enum by explaining that bands 1–6 are separate lists while 7-9 is a combined advanced band, and reinforces the 100-words-per-page meaning of page.

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 ('One page (100 words) of an HSK 3.0 vocabulary list'), plus ordering, per-word fields, and band structure. An agent can distinguish it from look_up_word and search_dictionary without opening any 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?

Explicitly routes pagination ('ask for later pages with the page argument') and names the alternatives for the single-word case ('use look_up_word or search_dictionary instead of scanning the lists'), including the reason not to use this tool.

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

All Dengdeng Chinese Dictionary 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.

Resources

Need Help?