Skip to main content
Glama
Sign In

OpenCidian: open Chinese ↔ Vietnamese dictionary (Hán Việt, pinyin, character breakdown)

by io.github.OpenCidian
OverviewDiscussionsAdmin

Annotate a Chinese text

annotate_text
Read-only

Splits Chinese text into words (longest match against the dictionary) and gives each its pinyin, Hán Việt per character, Vietnamese and English senses and entry id. kind is word, unknown (Chinese not in the dictionary: say so) or other (punctuation, Latin, digits). otherReadings > 0 means the word has more readings than the one shown: look it up when the reading matters. The split is by dictionary match, not grammar, and can be wrong (哪国人 comes out 哪 + 国人): check a split that changes the meaning.

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": {
      "text": "<text>"
    },
    "name": "annotate_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesChinese text, up to 2000 characters: a sentence, a lesson's dialogue, a sign.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only declare readOnlyHint, so the description carries the real burden and does it well: it discloses the algorithm (longest dictionary match, not grammar), its failure mode with a concrete example (哪国人 → 哪 + 国人), and an actionable check. It also decodes output fields (kind values, otherReadings) that annotations cannot supply.

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?

Front-loaded with the verb and core output, then caveats. Nearly every clause carries information, though the mid-block sequencing of `kind`, `otherReadings`, and the wrong-split warning is dense and would read better as separate short sentences or a list.

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?

With no output schema, the description takes on the job of explaining return values and does so completely: per-word pinyin, Hán Việt per character, senses, id, kind classification, and otherReadings. An agent has everything needed to call it and to interpret the response without guessing.

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?

There is only one parameter and schema coverage is 100%, with the schema already documenting the 2000-character limit and giving examples. The description adds only the framing that the input is segmented Chinese text, so it neither needs to nor does add much beyond the schema — the baseline 3 for full coverage applies.

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?

States a specific verb and resource ('Splits Chinese text into words') and enumerates exactly what each word yields: pinyin, Hán Việt, Vietnamese and English senses, entry `id`. This is clearly distinguishable from lookup/get_character, which would target a single entry rather than segmenting free text.

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 description — segment a Chinese sentence, dialogue, or sign — and it gives useful in-context guidance on interpreting output (unknown = not in dictionary, otherReadings > 0 = look it up, verify meaning-changing splits). However, there is no explicit when-to-use vs alternatives, e.g. no statement that lookup should be used for a single word already known.

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

All OpenCidian: open Chinese ↔ Vietnamese dictionary (Hán Việt, pinyin, character breakdown) toolsInspect
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