Skip to main content
Glama
FRANhss

Agent中国通

by FRANhss

中文文本清洗/脱敏

cn_text_normalize
Read-onlyIdempotent

Clean and normalize Chinese text by trimming whitespace, converting full-width to half-width characters, removing control characters, and optionally masking sensitive data like phone numbers, emails, ID numbers, and URL query parameters.

Instructions

清洗中文文本:空白归一化、全角半角转换、控制字符移除,并可选脱敏手机号/邮箱/身份证/URL 查询参数。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes待清洗文本。
trimNo是否 trim 首尾空白,默认 true。
normalizeWhitespaceNo是否归一化空白,默认 true。
fullWidthToHalfWidthNo是否全角转半角,默认 true。
removeControlCharsNo是否移除控制字符,默认 true。
maskPhoneNo是否脱敏中国大陆手机号。
maskEmailNo是否脱敏邮箱。
maskIdCardNo是否脱敏中国身份证号。
maskUrlQueryNo是否脱敏 URL 查询参数。
Behavior4/5

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

Annotations indicate readOnly, non-destructive, idempotent behavior. The description adds specific transformations (normalization, masking) that occur, which is beyond the annotations. No contradiction with annotations.

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 sentence with a list of operations. It is front-loaded with the main purpose and every phrase is meaningful. No redundant information.

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?

While there is no output schema, the description implies the result is the cleaned text. With rich schema and annotations, the description is complete enough for an agent to understand functionality. Minor gap: return format not detailed.

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% with each parameter described in Chinese. The description provides a summary but does not add new parameter-level meaning beyond the schema. Baseline 3 is appropriate.

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 the tool normalizes Chinese text with specific operations (whitespace normalization, full/half-width conversion, control character removal) and optional masking of sensitive data. The verb '清洗' (clean) and resource '中文文本' (Chinese text) are specific. No sibling tool performs text normalization, so it is well-distinguished.

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 implies when to use the tool: for cleaning Chinese text and optionally masking personal information. It does not explicitly state when not to use or provide alternatives, but given no similar sibling tools, the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FRANhss/Agent-'

If you have feedback or need assistance with the MCP directory API, please join our Discord server