Skip to main content
Glama

Pandawed — Chinese flashcards (HSK)

Первые слова набора

get_set_preview
Read-onlyIdempotent

Первые слова набора (до 30, у маленьких наборов — половина) с иероглифами, пиньинем и переводом на русский, плюс ссылка, где пройти весь набор карточками. Ключи: hsk1…hsk6, hsk7-9 (HSK 3.0), numbers, basic100, темы вида tema-colors и уроки учебников вида uch-301-1-05 — полный список даёт list_sets.

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": {
      "set": "<set>"
    },
    "name": "get_set_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
setYesКлюч набора из list_sets: hsk1, hsk7-9, tema-family, uch-301-1-01 и т. п.

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral detail beyond that: a hard cap of 30 items, half for small sets, and the presence of an outbound link in the result.

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?

Two sentences, front-loaded with what the caller gets before listing accepted key forms. The key enumeration is dense but each item is functional; there is no filler.

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 single-parameter read tool with no output schema, the description sufficiently characterizes the return payload (capped word list with three fields plus a link) and all valid key shapes. It could be slightly more explicit about ordering or truncation semantics, but nothing essential 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 schema's pattern plus description already enumerate the accepted key families and point to list_sets. The description mostly repeats those families, adding only the HSK 3.0 clarification for hsk7-9 and the tema-/uch- prefix conventions, which is marginal added meaning.

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 resource (the first words of a set) and exactly what is returned: hieroglyphs, pinyin, Russian translation, and a link to the full flashcard set. It also distinguishes itself from the sibling list_sets, which is named as the source of the complete key catalog.

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?

It makes the intended use clear: a lightweight preview of a set before going through it fully, with list_sets named for enumerating keys. It does not explicitly state when not to use it or whether any sibling returns the full set, so the guidance stops short of full when/when-not coverage.

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