Skip to main content
Glama
Sign In

Translate

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Translate

translate
Read-onlyIdempotent

Translate text between languages using a LibreTranslate instance you supply — pass _apiKey for libretranslate.com or _endpoint for a self-hosted server. For translation with no key of your own, call mymemory_translate instead.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "Hello, how are you?",
      "source": "en",
      "target": "es"
    },
    "name": "translate"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text to translate
sourceYesSource language code (e.g. "en" for English, "es" for Spanish)
targetYesTarget language code (e.g. "es" for Spanish, "fr" for French)

Output Schema

NameRequiredDescriptionDefault
sourceYesSource language code
targetYesTarget language code
original_textYesThe original text that was translated
translated_textYesThe translated text result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "source": "en",
+    "target": "es",
+    "text": "Hello, how are you?"
+  },
+  {
+    "source": "fr",
+    "target": "de",
+    "text": "Bonjour, comment allez-vous?"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "original_text": {
+      "description": "The original text that was translated",
+      "type": "string"
+    },
+    "source": {
+      "description": "Source language code",
+      "type": "string"
+    },
+    "target": {
+      "description": "Target language code",
+      "type": "string"
+    },
+    "translated_text": {
+      "description": "The translated text result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "source",
+    "target",
+    "original_text",
+    "translated_text"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "source": "en",
-    "target": "es",
-    "text": "Hello, how are you?"
-  },
-  {
-    "source": "fr",
-    "target": "de",
-    "text": "Bonjour, comment allez-vous?"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "original_text": {
-      "description": "The original text that was translated",
-      "type": "string"
-    },
-    "source": {
-      "description": "Source language code",
-      "type": "string"
-    },
-    "target": {
-      "description": "Target language code",
-      "type": "string"
-    },
-    "translated_text": {
-      "description": "The translated text result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "source",
-    "target",
-    "original_text",
-    "translated_text"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "original_text": {
+      "description": "The original text that was translated",
+      "type": "string"
+    },
+    "source": {
+      "description": "Source language code",
+      "type": "string"
+    },
+    "target": {
+      "description": "Target language code",
+      "type": "string"
+    },
+    "translated_text": {
+      "description": "The translated text result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "source",
+    "target",
+    "original_text",
+    "translated_text"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "source": "en",
+    "target": "es",
+    "text": "Hello, how are you?"
+  },
+  {
+    "source": "fr",
+    "target": "de",
+    "text": "Bonjour, comment allez-vous?"
+  }
+]
  5. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond that: it requires external credentials (_apiKey or _endpoint) and discloses that it calls an external translation service. It does not mention rate limits or failure behavior, so it falls short of a 5.

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, front-loaded with the action and dependency, followed by the routing alternative. Every clause earns its place; nothing is redundant.

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?

An output schema exists, so return values need not be explained, and the description covers the key operational prerequisite (own LibreTranslate credentials). The only gap is the unexplained mismatch between the mentioned _apiKey/_endpoint parameters and the schema, which lists only text/source/target.

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 description coverage is 100%, so the three parameters (text, source, target) are already fully documented with language-code examples. The description adds no further semantics for these parameters; it instead references _apiKey and _endpoint, which are not present in the input schema. Baseline 3 is appropriate when the schema carries the parameter documentation.

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?

States a specific verb and resource ('Translate text between languages') and immediately frames the required backend ('using a LibreTranslate instance you supply'). It explicitly names the sibling to use instead when no key exists, so an agent can distinguish it from mymemory_translate without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance (you have a LibreTranslate API key or self-hosted endpoint) and an explicit when-not-to-use alternative ('For translation with no key of your own, call mymemory_translate instead'). The routing condition is fully stated, not implied.

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

All Translate toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources