Skip to main content
Glama
Sign In

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

by io.github.OpenCidian
OverviewDiscussionsAdmin

One Chinese character

get_character
Read-only

Everything known about one character: Hán Việt readings (Thiều Chửu first, Unihan when Thiều Chửu has none), pinyin readings, a short English gloss, stroke count, radical, its parts (decomposition) and how it was formed (etymology: the meaning part and the sound part, each with its Hán Việt), and its traditional or simplified forms. Every field carries src. For the words a character is in, use words_with; for a character used as a word, lookup.

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": {
      "char": "<char>"
    },
    "name": "get_character"
  }
}

Input Schema

NameRequiredDescriptionDefault
charYesOne Chinese character, simplified or traditional (觉 or 覺).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint, so the description must carry the return-shape burden, and it does: it lists every returned field and states provenance rules (every field carries `src`, Thiều Chửu preferred with Unihan fallback). It does not say what happens when a character is unknown or partially covered, which is the remaining 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?

Field enumeration is front-loaded and the sibling routing is placed at the end where it belongs as a fallback. The opening sentence is long but each clause carries distinct information; no filler sentences.

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, the description correctly enumerates the return fields and their provenance, which is the critical missing piece otherwise. Only the not-found/partial-data behavior is left unstated for a tool whose whole purpose is aggregation.

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 coverage is 100% and the schema already documents the single `char` parameter including the simplified/traditional example. The description adds no syntax, format or constraint detail beyond that, so the baseline 3 for fully documented schemas 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?

The description names a specific resource ('one character') and enumerates exactly what is returned: Hán Việt readings, pinyin, gloss, stroke count, radical, decomposition, etymology and traditional/simplified forms. It also explicitly distinguishes itself from siblings words_with and lookup, so an agent can route correctly 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?

It names both alternatives and the condition selecting each ('For the words a character is in, use words_with; for a character used as a word, lookup'). The second clause is terse and slightly cryptic about how get_character differs from lookup, but the routing intent is explicit.

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