Skip to main content
Glama

Pandawed — Chinese flashcards (HSK)

Как будет слово по-китайски

how_to_say
Read-onlyIdempotent

Как сказать русское слово по-китайски: иероглифы, пиньинь, какой перевод когда выбирать, фразы с этим словом, частые вопросы и ссылка на страницу pandawed.ru/po-kitajski/ с озвучкой и порядком черт. Без слова — список всех слов, для которых есть страница.

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

Input Schema

NameRequiredDescriptionDefault
wordNoРусское слово, например «друг», «семья», «можно»; можно и иероглифами: 朋友

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld=false and idempotent, so safety needs no restating. The description adds genuine context beyond them: the exact payload of the response, an external pandawed.ru link with audio and stroke order, and the fallback behavior when no word is supplied. It does not say whether the source is a fixed bundled dictionary or how many entries the list contains, but for a read-only lookup tool that is a small gap.

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 the core purpose and the return contents, with the no-argument mode as a trailing qualifier. The middle enumeration of return components is dense but each item is informative; the sentence is somewhat overloaded before the second period, which keeps it from being a clean 5.

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, so the description must carry the return-value burden, and it does: it enumerates characters, pinyin, translation disambiguation, example phrases, FAQ and an external link. Combined with 100% schema coverage and full annotation coverage, an agent has enough to call it correctly; only the size/format of the no-word list is left implicit.

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% and the single 'word' parameter is already documented with limits and an example, so the baseline is 3. The description earns an extra point by explaining the semantics of omitting the parameter entirely (list-all mode), which the schema marks as non-required but does not explain. It also notes the word may be in Russian or characters, though the schema already says that.

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 and resource — it explains how a Russian word is said in Chinese and lists exactly what comes back (иероглифы, пиньинь, translation choices, phrases, FAQ, page link). The second sentence additionally separates the no-argument mode (full word list) from the lookup mode, so it is distinguishable from the article-oriented siblings without opening a schema.

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 final sentence gives explicit behavioral guidance for the optional-parameter case: omit the word and you get a list of every word that has a page. That covers the main ambiguity (what happens with no argument), but the description never references the sibling tools (search_articles, get_article) or states when a word lookup is preferable to searching an article.

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