Skip to main content
Glama

Search HSK words

search_words
Read-onlyIdempotent

Search HSK 3.0 words by level, topic tag, or pinyin (with or without tone marks or tone numbers). Returns at most 20 short matches per page. Give at least one of level, topic or pinyin.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1
levelNoHSK 3.0 level: 1-6, or "7-9" for the advanced band
topicNoTopic tag, e.g. food, travel, work, school, health, emotion
pinyinNoPinyin with or without tones, e.g. "jingyan", "jīngyàn", "jing1yan4"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/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 useful behavioral detail (max 20 results per page, short/truncated matches), but says nothing about match ordering, ranking, or how multiple filters combine (AND vs OR).

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 tight sentences: purpose, result cap, then the constraint. The required-input rule is placed last where it reads as an actionable check, and there is no redundant restatement of the name or title.

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?

No output schema exists, yet the description covers the result cap and the terseness of matches, which is the most important return-shape fact for a search tool. It leaves the returned fields and ordering unspecified, a modest gap for a query tool with fully documented inputs.

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 parameter formats are already documented, giving a baseline of 3. The description adds value the schema cannot express: pinyin accepts tone marks, no tones, or tone numbers, and at least one filter must be supplied — a cross-parameter constraint absent from the schema.

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 a specific verb+resource ("Search HSK 3.0 words") and enumerates the three filter axes (level, topic, pinyin), which lets an agent distinguish it from lookup-style or list-style siblings. It stops short of explicitly naming a contrasting sibling (e.g. lookup_word or hsk_level_wordlist) to sharpen the boundary.

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 at least one of level, topic or pinyin" is a genuine usage constraint since all four params are optional in the schema, telling the agent how to form a valid call. It does not name alternative tools or state when NOT to use this one, keeping it below the top band.

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