Skip to main content
Glama
oofengoo

MCP-Serve 多语言翻译服务

by oofengoo

translationI18n

Translate text between languages using the MCP-Serve multilingual translation service. This tool processes input text through external APIs for automatic language conversion and resource management.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYes

Implementation Reference

  • The handler function for the translationI18n tool. It uses regex to find content between ## markers, prepares params, optionally translates to English if port==5500, calls geti18n API, replaces the markers with aliases, and returns a text content block.
    async ({ input }) => {
      // 匹配所有 ##...## 的内容
      const regex = /##([\s\S]+?)##/g;
      let matches = input.matchAll(regex);
      let result = input;
      for (const match of matches) {
        const value = match[1];
        if (!value) continue;
        let params: Record<string, any> = {
          language: 1,
          autoAlias: true,
          value: value,
        };
        if (port === "5500") {
          params.valueEn = await TranslateToEn(value);
        }
        // 调用多语言接口
        const alias = await geti18n(params);
        if (alias) {
          result = result.replace(match[0], alias);
        }
      }
      return {
        content: [
          {
            type: "text",
            text: result,
          },
        ],
      };
    }
  • Input schema definition using Zod: expects a single string input.
    {
      input: z.string(),
    },
  • src/index.ts:13-49 (registration)
    Registration of the translationI18n tool on the McpServer instance.
    server.tool(
      "translationI18n",
      {
        input: z.string(),
      },
      async ({ input }) => {
        // 匹配所有 ##...## 的内容
        const regex = /##([\s\S]+?)##/g;
        let matches = input.matchAll(regex);
        let result = input;
        for (const match of matches) {
          const value = match[1];
          if (!value) continue;
          let params: Record<string, any> = {
            language: 1,
            autoAlias: true,
            value: value,
          };
          if (port === "5500") {
            params.valueEn = await TranslateToEn(value);
          }
          // 调用多语言接口
          const alias = await geti18n(params);
          if (alias) {
            result = result.replace(match[0], alias);
          }
        }
        return {
          content: [
            {
              type: "text",
              text: result,
            },
          ],
        };
      }
    );
  • Helper function that calls the /MultiLanguageResource/AddResource API to get the i18n alias for given params.
    async function geti18n(params: Record<string, any>) {
      
      const res = await http.post(
        "/MultiLanguageResource/AddResource",
        params,
        baseConfig
      );
      if (res.Data) {
        return res.Data.ResourceAlias;
      } else {
        return "";
      }
    }
  • Helper function that translates text to English via API, used conditionally in handler.
    async function TranslateToEn(text: string) {
      const res = await http.get(
        "/MultiLanguageResource/TranslateToEn",
        { text },
        baseConfig
      );
      return res;
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/oofengoo/mcp-serve-learn'

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