Skip to main content
Glama

Pandawed — Chinese flashcards (HSK)

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

list_sets
Read-onlyIdempotent

Наборы pandawed.ru: HSK 3.0 по уровням (1–6 и 7–9), тематические наборы (семья, еда, цвета, числа и ещё два десятка) и уроки учебников («Разговорная китайская речь 301», Developing Chinese) — с числом слов и ссылкой на занятие. Можно выбрать группу: hsk, temy (темы) или uchebniki (учебники).

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

Input Schema

NameRequiredDescriptionDefault
groupNoКакую группу показать; без неё — все

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare it read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description then adds genuinely new behavioral context that annotations cannot carry: each set comes with a word count and a link to the lesson, which tells the agent the shape of the payload despite there being no output schema.

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 tool returns before naming the filter. The catalogue enumeration is slightly dense but earns its place by letting an agent check whether a needed set type exists.

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 one-optional-parameter, read-only listing tool with rich annotations and no output schema, the description supplies everything needed: what is listed, what fields accompany each item, and how to filter. No obvious gap remains.

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%, so the single enum parameter is already fully documented, including the default of 'all'. The description only restates the three enum values and glosses temy/uchebniki, adding marginal meaning beyond 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 names a specific verb and resource ('Наборы pandawed.ru') and enumerates the exact catalogue it returns (HSK 3.0 levels 1–6 and 7–9, thematic sets, textbook lessons). It does not contrast itself with siblings such as get_set_preview or list_articles, so an agent must infer that this is the browse-all endpoint.

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?

Usage is only implied: 'Можно выбрать группу' tells the agent it may scope the listing but never states when to call this versus previewing a single set or searching. No exclusions, prerequisites, or alternative routes are given.

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