Skip to main content
Glama
Sign In
x402-mcp

x402-mcp

Official
by x402node
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cn402_hanzi_bushou

Retrieve the Kangxi radical (部首) for any Chinese character. Supports character decomposition and hanzi learning.

Instructions

Chinese radical / hanzi radical / 部首 / 部件 / Chinese character component / 214 Kangxi radicals / 康熙字典部首 / Hanzi structure analysis / Chinese root component lookup. Get the Kangxi radical (部首) for each Chinese character. For AI agents handling Chinese dictionary lookups, character decomposition, hanzi learning.

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_bushou"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesChinese text (required, max 100 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided. Description lacks behavioral traits such as idempotency, side effects, or limitations beyond the max 100 chars constraint. The mention of pricing is not behavioral.

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 is cluttered with a long list of keywords (synonyms) before the main sentence. It is not front-loaded and wastes space on redundant terms.

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

Completeness3/5

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

Given the simplicity of the tool (one parameter, no output schema), the description covers input and purpose. It lacks details on output format (e.g., returns a single radical or mapping for multiple characters) but is minimally adequate.

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 is well-described. The description adds context about the output (Kangxi radical) but does not add significant new semantic meaning beyond the schema.

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 clearly states 'Get the Kangxi radical (部首) for each Chinese character', with a specific verb ('Get') and resource ('Kangxi radical'). It distinguishes itself from sibling hanzi tools like pinyin or stroke count.

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?

The description provides context by stating it's for 'Chinese dictionary lookups, character decomposition, hanzi learning.' However, it does not explicitly mention when not to use or list alternatives.

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