MandarinClips MCP

search_dialogue_clips

Search authentic Chinese cinema dialogue clips by Chinese characters or pinyin. Returns 3-turn conversational context (Previous, Target, Next), standard pinyin, English subtext, and source movies/shows.

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": {
      "query": "<query>"
    },
    "name": "search_dialogue_clips"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Number of example clips to return (1-10, default 3)
`query`	Yes	Chinese characters or pinyin (e.g., '算了吧', 'suan le ba', '折腾')

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the return payload well (3-turn Previous/Target/Next context, standard pinyin, English subtext, source movie/show), which is genuinely useful. It says nothing about read-only nature being implicit, result quality, empty-result behavior, or any rate/permission constraints.

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?

Two sentences, zero waste, with the capability stated first and the return shape second. Nothing is redundant or padded.

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?

With no output schema and no annotations, the description fills the important gap by explaining the return structure (three-turn context plus pinyin, English subtext, sources). Parameter semantics are fully covered by the schema. It stops short of describing matching behavior (exact vs fuzzy) or what happens on no match.

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 description coverage is 100%, so both `query` (characters or pinyin, with examples) and `limit` (1-10, default 3) are already fully documented. The description's 'by Chinese characters or pinyin' merely echoes the schema without adding syntax or matching-behavior detail, so the baseline 3 applies.

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 (search) and a specific resource (authentic Chinese cinema dialogue clips), plus the input modality (Chinese characters or pinyin). An agent can tell this apart from get_grammar_pattern and get_hsk_vocabulary by resource type, but the description never explicitly contrasts with those siblings.

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: use this when you want authentic example sentences from film/TV rather than grammar patterns or vocabulary entries. There is no explicit statement of when to prefer this over the sibling tools, nor any exclusions or prerequisites.

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?