Skip to main content
Glama

Libretranslate

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Translate

translate
Read-onlyIdempotent

Translate text. Source can be "auto" to auto-detect. Returns translated text and the detected source (if applicable).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesText to translate
formatNotext (default) | html
sourceNoSource language code or "auto" (default "auto")
targetYesTarget language code (e.g., "es", "fr", "ja")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesOriginal text that was translated
formatYesFormat type (text or html)
sourceYesSource language code or 'auto'
targetYesTarget language code
detected_sourceYesAuto-detected source language code or null
translated_textYesTranslated text or null if unavailable
detected_confidenceYesConfidence score for detected language or null

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "target": "es",
+    "text": "Hello, how are you?"
+  },
+  {
+    "format": "html",
+    "source": "en",
+    "target": "fr",
+    "text": "<p>Welcome to our website</p>"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "detected_confidence": {
+      "description": "Confidence score for detected language or null",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "detected_source": {
+      "description": "Auto-detected source language code or null",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "format": {
+      "description": "Format type (text or html)",
+      "type": "string"
+    },
+    "source": {
+      "description": "Source language code or 'auto'",
+      "type": "string"
+    },
+    "target": {
+      "description": "Target language code",
+      "type": "string"
+    },
+    "text": {
+      "description": "Original text that was translated",
+      "type": "string"
+    },
+    "translated_text": {
+      "description": "Translated text or null if unavailable",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "text",
+    "source",
+    "target",
+    "format",
+    "translated_text",
+    "detected_source",
+    "detected_confidence"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive. The description adds behavioral context by explaining the 'auto' source default and that the detected source is returned when applicable. 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?

Two concise sentences with no redundancy. The key behaviors (auto source, return value) are front-loaded efficiently.

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

Completeness5/5

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

For a simple translation tool with a rich schema and output schema, the description covers the essential behavior (auto-detection, return format) without needing to explain parameters or return values in detail.

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 covers 100% of parameters with descriptions. The description only reiterates the 'auto' source behavior already in the schema, adding no new semantic information beyond what is structured.

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?

Clear verb+resource: 'Translate text' immediately states the tool's function. It also notes auto-detection of source language and return value, distinguishing it from sibling tools like detect_language which only detects language.

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

Usage Guidelines3/5

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

The description implies usage for translation but does not explicitly contrast with related tools (e.g., detect_language) or state when not to use it. There is no exclusion or alternative mention, so guidance is only implicit.

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

All Libretranslate 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