Skip to main content
Glama

Look up an HSK word

lookup_word
Read-onlyIdempotent

Look up one Chinese word from the HSK 3.0 syllabus: pinyin, level, part of speech, English meaning, an example sentence, and how its level changed from HSK 2.0. Use when the user asks what a word means or which HSK level it is.

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

Input Schema

NameRequiredDescriptionDefault
wordYesThe word in Chinese characters, simplified or traditional, e.g. 经验

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, closed-world lookup, so the safety profile is covered. The description adds real value beyond that by disclosing the payload contents (including the HSK 2.0 level-change field) and pinning the lookup domain to the HSK 3.0 syllabus, which implies misses for out-of-syllabus words; it does not state what happens on a not-found word.

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: the first states the operation and full return set, the second states the trigger. The most load-bearing information (what is returned) is front-loaded.

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, and the description compensates by enumerating every returned field, so an agent knows precisely what it gets. For a single-parameter read-only lookup, nothing needed to call it correctly is missing.

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 single `word` property already documents character input with an example, so the schema carries the weight. The description adds only the light constraint that the word must be from the HSK 3.0 syllabus, which is a marginal addition; baseline 3 applies.

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?

Names a specific verb and resource ("look up one Chinese word from the HSK 3.0 syllabus") and enumerates exactly what comes back: pinyin, level, part of speech, English meaning, example sentence, and HSK 2.0 delta. The singular "one word" implicitly separates it from list-style siblings like hsk_level_wordlist and search_words, but no sibling is named explicitly.

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?

The closing sentence gives a concrete trigger: the user asks what a word means or which HSK level it is. That is a clear when-to-use condition, but there is no when-not guidance and no explicit routing to alternatives such as search_words for partial or unknown words.

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