Skip to main content
Glama

Compare HSK 2.0 and 3.0

compare_hsk2_hsk3
Read-onlyIdempotent

Explain how a word or a whole level changed between the HSK 2.0 and HSK 3.0 syllabi: new, moved up, moved down, unchanged, or dropped, with counts for a level. Give either word or level.

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

Input Schema

NameRequiredDescriptionDefault
wordNoA word in Chinese characters
levelNoHSK 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.4/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 safety profile is covered. The description adds genuine behavioral value by stating what the response contains: a change classification and counts for a level. It does not discuss pagination, error handling for unknown words, or output formatting, which keeps it below 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with zero filler: the first front-loads the operation and its result taxonomy, the second states the input constraint. Nothing is repeated from the title or annotations.

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?

For a two-parameter read-only tool with no output schema, the description covers purpose, inputs, and the shape of the result, which is close to sufficient. The remaining gap is the unaddressed edge cases: passing both parameters or neither, and what a level-mode count response looks like.

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 both parameters are already documented, giving a baseline of 3. The description goes beyond the schema by framing them as mutually exclusive alternatives (word OR level), which the schema itself does not express since both are optional.

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?

The description names a specific verb (explain how ... changed) and a precise resource (a word or a whole level across HSK 2.0 vs 3.0), and enumerates the exact outcome taxonomy: new, moved up, moved down, unchanged, dropped, plus counts. That taxonomy clearly separates it from siblings like hsk_level_wordlist or lookup_word, which return word data rather than a cross-syllabus diff.

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?

"Give either word or level" gives concrete input-mode guidance and implies the two parameters are alternatives, which is essential given that neither is required. It stops short of naming when to prefer this over lookup_word or hsk_level_wordlist, and does not say what happens if both or neither is supplied.

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