Skip to main content
Glama

Talkhao

Words in an HSK list

hsk_words
Read-onlyIdempotent

What is in an HSK list: an HSK level (1-6), an HSK 3.0 band (1-6 or 7-9) or a topic (numbers, food and drink, family, ...). Answers with the number of words, the first five with their pinyin and meaning, the list's Talkhao page and its practice link; when the learner's account is connected, each word's state on their trail. Give exactly one of level, band or topic.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hsk_words"
  }
}

Input Schema

NameRequiredDescriptionDefault
bandNoAn HSK 3.0 band: 1-6 or 7-9
levelNoAn HSK level, 1-6 (HSK 2.0)
topicNoA topic, in English: numbers, food and drink, family, animals, ...

Output Schema

NameRequiredDescriptionDefault
urlYesThe list's Talkhao page
kindYeslevel, band or topic
countYesThe list's words, as its page counts them (one per word page)
labelYesThe list's name, in English
wordsYesThe first five, in the page's order
languageYesThe language the meanings are in: en, es, id, th or vi
practise_urlYesPractise the whole list on Talkhao
language_noteNoSet when the learner's locale has no translations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false. Beyond those, the description discloses return content (number of words, first five with pinyin and meaning, Talkhao page, practice link) and the account-dependent 'state on their trail,' adding useful behavioral context. It does not cover pagination or error behavior, but the safety profile is already in annotations.

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 compact, moving from purpose to return summary to the exactly-one constraint. It is somewhat dense and punctuation-heavy, but no sentence is wasted.

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 simple read-only lookup tool with a full output schema, the description covers the selectable inputs, the one-selector constraint, and the account-dependent addition. Nothing essential for correct invocation is missing.

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 a real constraint absent from the schema: exactly one of level, band, or topic must be supplied even though the schema marks all three optional. It also reinforces the HSK 2.0 vs 3.0 distinction and gives English topic examples.

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 states the resource (HSK list contents) and the three selectors (level, band, topic), which lets an agent distinguish it by scope from look_up_word or save_words. It does not explicitly name those siblings as alternatives, so the differentiation is implicit rather than stated.

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?

It implies the tool is for inspecting an HSK list and adds the invocation constraint 'Give exactly one of level, band or topic.' It gives no explicit when-to-use guidance against siblings such as look_up_word or my_progress, and no when-not conditions.

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