Skip to main content
Glama
Sign In

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

by io.github.OpenCidian
OverviewDiscussionsAdmin

About OpenCidian's data

about
Read-only

The dataset's version and build date, its licence (CC BY-SA 4.0), the full attribution to quote when reusing it, and every source with its pinned version and licence (CC-CEDICT, CVDICT, Thiều Chửu, Unihan, Make Me a Hanzi, the HSK lists). Use it to say where an answer comes from or how to cite OpenCidian.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "about"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds meaningful behaviour beyond that: the response is a fixed metadata record covering version, build date, licence, attribution, and every upstream source with pinned versions and licences, which tells an agent the payload is static and safe to surface verbatim. It stops short of stating payload size or formatting.

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?

Two sentences, both front-loaded and claim-bearing, with no filler. The parenthetical source list is dense but each named source is genuinely useful for judging whether the answer covers a given dictionary.

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 parameters and no output schema, the description must carry the return-value burden and it does, enumerating the fields an agent will receive. It could note the shape or rough size of the response, but nothing essential to calling it correctly is missing.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate. The baseline of 4 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 enumerates the actual resource contents (dataset version and build date, CC BY-SA 4.0 licence, attribution string, per-source pinned versions and licences) which makes the tool unambiguously a metadata/about endpoint. It does not explicitly name a sibling it differs from, but the enumerated content makes overlap with get_character or lookup implausible.

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?

'Use it to say where an answer comes from or how to cite OpenCidian' states a concrete triggering situation for calling the tool. There are no explicit when-not-to-use notes or named alternatives, but the guidance is clear enough that an agent knows to reach for it only for provenance/citation questions.

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