Skip to main content
Glama
Sign In

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

by io.github.OpenCidian
OverviewDiscussionsAdmin

Look up a Chinese word

lookup
Read-only

Dictionary entries for a Chinese word, a pinyin syllable or a Vietnamese word: simplified and traditional forms, pinyin, Hán Việt per character (Thiều Chửu), Vietnamese senses (CVDICT), English senses (CC-CEDICT), HSK level. Every field carries src, the source it came from. kinds says how the query was read and each entry's match which reading found it. vi: null means CVDICT has no Vietnamese for that word: say so, don't translate the English as if it were the dictionary's. No entries means the word isn't in the dictionary: say so, don't guess.

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": {
      "q": "<q>"
    },
    "name": "lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesChinese characters (觉得, 覺得), pinyin with or without tones (jué de, jue2 de5, jue de) or Vietnamese (cảm thấy).
byNoForce how q is read. Leave out to let the server tell hanzi, pinyin and Vietnamese apart.
limitNoEntries to return, 1-50 (default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the rest, and it does: per-field `src` provenance, `kinds` explaining how the query was interpreted, per-entry `match`, and the meaning of `vi: null`. It is explicit that an empty result means the word is absent and must not be guessed at. It stops short of describing ordering or pagination beyond the schema's limit.

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?

One dense paragraph, front-loaded with what is returned, then provenance, then result-interpretation rules. Every sentence carries information; the only mild cost is that the field enumeration is long, but it substitutes for a missing output schema.

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?

There is no output schema, and the description compensates by describing the returned fields, the source-attribution convention, per-entry match provenance, and the two edge cases (null Vietnamese, zero entries). Nothing an agent needs to call and correctly report results appears to be missing.

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 q, by and limit are already fully documented in the schema, including the enum and the default/max for limit. The description adds conceptual context about how the query can be read (`kinds`) but does not explain the `by` override or limit behavior beyond what the schema gives, so 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?

States a specific resource and its returned fields: dictionary entries with simplified/traditional forms, pinyin, Hán Việt, Vietnamese and English senses, HSK level, for three query types (hanzi, pinyin, Vietnamese). An agent can tell what comes back without opening the schema. It does not name or contrast with siblings like get_character or search_meaning, so it falls short of full sibling differentiation.

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 enumerated query types rather than stated as when-to-use vs an alternative tool. The closing sentences give valuable handling rules (say when vi is null, say when no entries are found), but they govern interpreting results, not selecting this tool over get_character or search_meaning.

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