Skip to main content
Glama

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, deepl_translate covers the same languages.

Input Schema

TableJSON 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

TableJSON 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, and destructiveHint. The description adds behavioral context by requiring a user-supplied API key or endpoint, which is not covered by annotations. It does not elaborate on rate limits or errors, but this is acceptable given the annotation coverage.

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 primary action, and every sentence provides distinct value: the first explains the mechanism, the second offers an alternative. No redundancy or fluff.

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?

Given the output schema exists and annotations cover safety, the description is sufficient for effective selection and invocation. It addresses the key prerequisite (API key/endpoint) and alternative tool. A minor gap is not mentioning how to discover language codes, but sibling tools like list_languages cover that.

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% for text, source, and target, so the description does not need to repeat those. It adds mentions of _apiKey and _endpoint, but these are not present in the input schema, which could confuse parameter handling. Still, the core parameters are self-explanatory, and the description adds some operational context.

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's function: 'Translate text between languages using a LibreTranslate instance you supply'. It specifies the resource (text translation) and distinguishes it from siblings by highlighting the LibreTranslate backend requirement and the alternative deepl_translate.

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?

Provides explicit when-to-use guidance: use when you have an API key or endpoint, and explicitly directs users without a key to 'deepl_translate' as an alternative. This gives clear usage context and an exclusion condition.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources