Skip to main content
Glama

HSK level word list

hsk_level_wordlist
Read-onlyIdempotent

List the words of one HSK 3.0 level in syllabus order, 50 per page, with pinyin and a short English meaning. Use for study lists; for the full list point the user to the download link.

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": {
      "level": "<level>"
    },
    "name": "hsk_level_wordlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 50 words per page
levelYesHSK 3.0 level: 1-6, or "7-9" for the advanced band

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds genuine context beyond that: fixed 50-per-page pagination, syllabus ordering, the pinyin/meaning payload, and the redirect to a download link for bulk needs.

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, zero filler, with the core behavior front-loaded and the alternative path in the trailing clause.

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

Completeness4/5

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

With no output schema, the description carries the return-value burden and does so by naming fields, ordering, and page size. It omits how many words a level contains or how an agent knows pagination has ended, which would help an agent plan multi-page study lists.

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

Parameters3/5

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

Schema coverage is 100% and the schema itself documents page number, page size, and the level enum including "7-9". The description only restates '50 per page' and adds nothing about the level values beyond what the schema already provides, so baseline 3 applies.

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 ('List the words of one HSK 3.0 level'), plus ordering, page size, and returned fields. The 'use for study lists' cue separates browsing a level from word-lookup tools like lookup_word or search_words.

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

Usage Guidelines4/5

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

Gives both a when-to-use ('study lists') and a when-not/alternative path ('for the full list point the user to the download link'). It stops short of naming schema siblings such as search_words or lookup_word, so routing against them is left implicit.

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