Skip to main content
Glama
liyb-gz

tinci-mcp

by liyb-gz
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_rhyming_characters

Find Chinese characters that rhyme with a given character for Cantonese lyric writing. Returns characters sharing the same Jyutping final, with optional tone or tone group filtering.

Instructions

Find characters that rhyme with the input character for lyrics composition.

Returns characters sharing the same Jyutping final (韻母) as the input character. This is essential for writing Cantonese lyrics where rhyming is based on the final sound of syllables.

Args: character: A single Chinese character to find rhymes for tone_filter: How to filter results by tone: - "all": Return all rhyming characters regardless of tone - "same": Only return characters with the exact same tone number - "group": Return characters in the same tone group (e.g., in the 0243 system, tones 1, 2 and 7 are in the same group (3); tones 3, 5 and 8 are in the same group (4); tones 6 and 9 are in the same group (2)) system: Tonal classification system for "group" filtering and tone display (1056 or 0243) limit: Maximum number of rhyming characters to return (default 50) target_tone: If specified, find rhyming characters with this specific tone (1-9). Overrides tone_filter. Example: character="泉" (tone 4), target_tone=1 returns rhyming characters with tone 1. target_group: If specified, find rhyming characters in this tone group. Overrides tone_filter. For 0243 system: "0" (tone 4), "2" (tones 6,9), "3" (tones 1,2,7), "4" (tones 3,5,8). Example: character="泉" (group 0), target_group="3" returns rhyming characters with tones 1, 2, or 7.

Returns: Dictionary with: - input: Info about the input character (character, jyutping, tone, tone_group) - final: The jyutping final (韻母) used for matching - rhymes: List of rhyming characters with their jyutping and tone info - count: Number of rhyming characters returned - total_count: Total available (before limit) - target_tone: (if specified) The target tone used for filtering - target_group: (if specified) The target group used for filtering

Example: Input: character="來", tone_filter="all" Returns rhyming characters like 愛 (oi3), 外 (ngoi6), 改 (goi2), etc. that share the same "oi" final.

Input: character="泉", target_tone=1
Returns rhyming characters with final "yun" but with tone 1.

Input: character="泉", target_group="3"
Returns rhyming characters with final "yun" but with tones 1, 2, or 7 (group 3).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
systemNo0243
characterYes
target_toneNo
tone_filterNoall
target_groupNo

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

No annotations, so description carries full burden. It discloses that it matches on final, explains tone filtering, systems, and override behavior. No destructive or permission info, but for a read tool this is sufficient.

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?

The description is lengthy but well-structured with sections for purpose, args, returns, and examples. Nearly every sentence adds value given the complexity of tone filtering and grouping.

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?

Covers all parameters, return format, and provides multiple examples. No output schema but description includes detailed return keys. Could mention error handling or input validation, but overall complete for a read tool.

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

Parameters5/5

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

Schema coverage is 0%, so description explains all 6 parameters in detail, including enums, defaults, and override relationships. Examples clarify usage. This adds significant value beyond schema.

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 clearly states the tool finds characters that rhyme with the input character for lyrics composition, based on Jyutping final. It distinguishes from sibling tools (get_jyutping, get_tone_pattern) by focusing on rhyming.

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 description implies usage for rhyming needs and provides examples. It does not explicitly contrast with siblings but context makes it clear. Slightly lacking explicit when-not-to-use guidance, but adequate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/liyb-gz/tinci-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server