Skip to main content
Glama

Get a Chinese character

get_character
Read-onlyIdempotent

Get one Chinese character: pinyin, radical, stroke count, components (when known), its HSK character and writing levels, and common HSK words that use it. Includes a link to a stroke-order animation page when one exists.

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": {
      "char": "<char>"
    },
    "name": "get_character"
  }
}

Input Schema

NameRequiredDescriptionDefault
charYesOne Chinese character, e.g. 把

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 already establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile needs no restating. The description adds real value beyond them by disclosing the shape of the response and flagging that components and the stroke-order animation link are conditional ("when known", "when one exists"). It does not say what happens for an unrecognized or non-Chinese input, which is the main remaining gap.

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?

Two sentences, both front-loaded with the most useful information: the resource first, then the field inventory, then the conditional extras. No filler, no repetition of the title or annotations.

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 output schema, the description correctly carries the burden of describing return values and does so thoroughly, including conditional fields. For a one-parameter read tool this is nearly complete; only error/miss behavior for invalid input is left unstated.

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% and the single parameter is documented with an example (把). The description only restates the parameter as "one Chinese character" and adds no format, encoding, or validation meaning beyond the schema — baseline 3 for a one-parameter tool whose schema does the work.

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 uses a specific verb ("Get") and a precise resource ("one Chinese character") and enumerates the returned data: pinyin, radical, stroke count, components, HSK character/writing levels, and HSK words. Singular-character scope implicitly separates it from plural word tools like search_words or lookup_word, but no sibling is named.

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?

The single-character scope and field list make the intended use inferable, but there is no explicit when-to-use statement and no guidance on when to prefer lookup_word or search_words instead. An agent must infer the boundary from the words "one Chinese character" alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources