Skip to main content
Glama
Sign In
x402-mcp

x402-mcp

Official
by x402node
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cn402_hanzi_s2t

Convert Simplified Chinese text to Traditional Chinese (Taiwan standard) using OpenCC for accurate character set conversion.

Instructions

Simplified to Traditional Chinese converter / 简体转繁体 / 简繁转换 / mainland to Taiwan Chinese / Chinese character set conversion / GB to BIG5 / OpenCC converter / Hanzi simplified traditional / Chinese localization. Convert Simplified Chinese text to Traditional Chinese (Taiwan standard).

Price: unknown on Base (auto-paid in USDC).

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

Input Schema

NameRequiredDescriptionDefault
textYesSimplified Chinese text (required, max 100 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior1/5

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

No annotations provided, and the description adds no behavioral traits beyond the input schema. It does not disclose rate limits, idempotency, output format, or any side effects.

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

Conciseness2/5

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

The description begins with a long list of redundant synonyms, then the functional sentence. The price information is irrelevant. Not front-loaded, and includes unnecessary fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given one parameter and no output schema, the description lacks completeness. It does not specify output format, error handling, or character set details for the conversion result.

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% for the single parameter, which already documents the parameter. The description adds synonyms but no extra semantic meaning beyond what the schema provides.

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 clearly states the tool converts Simplified Chinese to Traditional Chinese (Taiwan standard). It uses specific verb and resource, and the sibling 't2s' implies the reverse, so purpose is clear, but not explicitly differentiated.

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?

No guidance on when to use this tool vs alternatives. Mentions price but not usage context, prerequisites, or exclusions. Sibling tools exist but no comparison.

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

Deploy Server

Other Tools