jieba-mcp

Convert Simplified / Traditional Chinese

convert_chinese

Read-only

Convert Chinese text between Simplified and Traditional scripts, including Taiwan and Hong Kong standards, with phrase-level conversion for regional wording.

Instructions

Convert between Simplified and Traditional Chinese.

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": "convert_chinese"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes	Chinese text to process.
`config`	No	OpenCC conversion: s2t / t2s (Simplified <-> Traditional), s2tw / tw2s (Taiwan standard), s2twp / tw2sp (Taiwan, with phrases such as 软件 <-> 軟體), s2hk / hk2s (Hong Kong).	s2t

Output Schema

Name	Required	Description	Default
`text`	Yes	Converted text.
`config`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 11, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered. The description adds no behavioral context beyond the basic conversion purpose, such as idempotency, default direction, or handling of regional variants.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no wasted wording. It is appropriately sized for a simple, well-schema-documented converter.

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?

The tool is simple, with only two parameters, full schema description coverage, annotations, and an output schema. The description is complete enough for an agent to identify the tool, though it could briefly mention the configurable regional variants already covered by the schema.

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%, and the schema fully documents the text parameter and all conversion config enum values with examples. The description adds no parameter meaning beyond what the schema already provides, so the baseline of 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?

The description states a specific verb (Convert) and resource (Simplified and Traditional Chinese), making the tool's function immediately clear. It does not explicitly distinguish itself from siblings like segment or pos_tag, but those tasks are clearly different.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use, when-not-to-use, or alternative guidance. Usage is only implied by the tool name and the obvious conversion task, leaving the agent to infer whether this is appropriate versus other sibling tools.

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

Deploy Server