Skip to main content
Glama

translate_en2zh

Read-only

Translate English text arrays into Chinese while preserving input length and order, returning one Chinese translation per item.

Instructions

英译中 Returns: { words }:与输入等长的中文译文字符串数组。

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": {
      "words": "<words>"
    },
    "name": "translate_en2zh"
  }
}

Input Schema

NameRequiredDescriptionDefault
wordsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations declare readOnlyHint=true and openWorldHint=true, so the main safety profile is already known from the structured data. The description adds genuinely useful behavioral context: it says the return value is an array of Chinese strings with the same length as the input, implying element-wise translation with one output per input string. It does not mention batch size limits, failure handling, or whether mixed-language input is tolerated.

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

Conciseness4/5

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

Two compact clauses: the purpose first, then the return shape. Nothing is padded or redundant, and the most important information leads. It is terse almost to the point of being cryptic because of the compressed punctuation, but no sentence is wasted.

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?

For a one-parameter translation utility with no output schema, the definition covers direction, the shape of the input, and the shape of the result. The remaining gaps — limits, error behavior, whether non-English input is accepted — are minor for a tool this simple, though they would still help.

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?

There is a single required parameter, `words`, and schema description coverage is 0%, so the schema contributes nothing about meaning. The description is useful only for showing that the output is as long as the input, which implies that each string in `words` is translated independently. It nonetheless does not confirm that the input must be English text, nor does it rule out restrictions on empty strings or very large arrays.

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 names the direction of translation (英译中 = English to Chinese) and the resource being transformed, which is more specific than the title alone. It does not explain how it differs from any other tool, but among the listed sibling tools none are translation-like, so the risk of confusion is low.

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 statement of when to use this tool, when not to, or any prerequisite such as whether the input must be English and what happens if it is already Chinese. The only implicit guidance is the translation direction itself.

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