MandarinClips MCP

get_hsk_vocabulary

Retrieve official HSK 3.0 Chinese vocabulary details and cinema video examples by standard word slug or HSK level (1 to 7-9).

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": {
      "word_or_slug": "<word_or_slug>"
    },
    "name": "get_hsk_vocabulary"
  }
}

Input Schema

Name	Required	Description	Default
`word_or_slug`	Yes	Chinese word or slug (e.g., '爱', 'ai-1', '你好')

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations are provided, so the description must carry behavioral disclosure. 'Retrieve' implies a read operation and it discloses the content returned (vocabulary details and cinema examples), but it does not describe return structure, permissions, rate limits, or whether video examples are always included.

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?

The description is a single front-loaded sentence with no filler. Every clause attempts to convey purpose or input modes, though one input claim is inaccurate against the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read tool with a fully documented schema, the description is adequate but not complete. It omits return-format context and incorrectly advertises level-based lookup, which is not supported by the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents the single parameter with examples. However, the description introduces an unsupported 'HSK level (1 to 7-9)' input mode that has no corresponding parameter, which could mislead an agent trying to filter by level.

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 and resource: retrieve official HSK 3.0 Chinese vocabulary details and cinema video examples. It is clear what the tool returns, but it does not distinguish itself from siblings like search_dialogue_clips, and the claimed HSK-level lookup mode is not reflected in the schema.

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 implied by the vocabulary-lookup framing, but there is no explicit when-to-use guidance, no mention of when to use get_grammar_pattern or search_dialogue_clips instead, and no prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All MandarinClips MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?