Skip to main content
Glama
Sign In

Blackwood State

by io.github.Blackwood-State
OverviewDiscussionsAdmin

Translate text

blackwood_text_translate
Read-onlyIdempotent

Use when you need to translate text, a language translation or a text translation of a sentence or paragraph between two languages. Do not use for formatting that must be preserved, certified or legal translation, or speech (transcribe first). Returns JSON with text translation between about 100 languages by Meta M2M100 1.2B on Workers AI: the translated text with the source and target languages used for 0.012 USDC per call. Typical response time 5000 ms (p95). Category: Inference.

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": {
      "text": "<text>",
      "to": "<to>"
    },
    "name": "blackwood_text_translate"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesTarget language as an ISO 639-1 code, e.g. es, fr, pt, de, ja, zh
fromNoSource language as an ISO 639-1 code (default en)
textYesText to translate, e.g. Pay only for the requests you make (up to 2000 characters)
response_formatNoconcise (the default when omitted) keeps the JSON short: long fields such as base64 images or audio come back as separate image/audio content blocks and other long strings are cut with a marker; detailed returns the full JSON

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "from": {
-        "type": "string"
-      },
-      "model": {
-        "type": "string"
-      },
-      "to": {
-        "type": "string"
-      },
-      "translatedText": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "translatedText",
-      "from",
-      "to",
-      "model"
-    ],
-    "type": "object"
-  },
-  {
-    "description": "x402 PaymentRequired (returned with isError when payment is needed)",
-    "properties": {
-      "accepts": {
-        "items": {
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "error": {
-        "type": "string"
-      },
-      "extensions": {
-        "type": "object"
-      },
-      "resource": {
-        "type": "object"
-      },
-      "x402Version": {
-        "type": "integer"
-      }
-    },
-    "required": [
-      "x402Version",
-      "accepts"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "from": {
+        "type": "string"
+      },
+      "model": {
+        "type": "string"
+      },
+      "next": {
+        "additionalProperties": false,
+        "description": "Suggested next paid call in the same family (call it in a loop when the task continues)",
+        "properties": {
+          "method": {
+            "enum": [
+              "GET",
+              "POST"
+            ],
+            "type": "string"
+          },
+          "sample": {
+            "description": "Free fixed sample of the whole family",
+            "type": "string"
+          },
+          "service": {
+            "description": "Service id of the suggested next paid call",
+            "type": "string"
+          },
+          "tool": {
+            "description": "MCP tool name of the same call",
+            "type": "string"
+          },
+          "url": {
+            "description": "Paid route of the next call",
+            "type": "string"
+          },
+          "useWhen": {
+            "description": "When the next call is the right one",
+            "type": "string"
+          }
+        },
+        "required": [
+          "service",
+          "tool",
+          "method",
+          "url",
+          "useWhen",
+          "sample"
+        ],
+        "type": "object"
+      },
+      "to": {
+        "type": "string"
+      },
+      "translatedText": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "translatedText",
+      "from",
+      "to",
+      "model"
+    ],
+    "type": "object"
+  },
+  {
+    "description": "x402 PaymentRequired (returned with isError when payment is needed)",
+    "properties": {
+      "accepts": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "error": {
+        "type": "string"
+      },
+      "extensions": {
+        "type": "object"
+      },
+      "resource": {
+        "type": "object"
+      },
+      "x402Version": {
+        "type": "integer"
+      }
+    },
+    "required": [
+      "x402Version",
+      "accepts"
+    ],
+    "type": "object"
+  }
+]
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower, yet the description adds genuinely actionable context: 0.012 USDC per call, p95 latency of 5000 ms, the underlying model/family and language coverage (~100 languages), and the shape of the JSON result. It does not mention failure modes (unsupported language pair, >2000 char input), which is the only real gap.

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?

Front-loaded with the use-when clause and every trailing clause (cost, latency, model, return shape) earns its place for a paid inference tool. The opening 'text, a language translation or a text translation of a sentence or paragraph' is redundant restatement that could be cut without loss.

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?

With an output schema present, return-value description is optional, and the description still summarizes it. Combined with cost, latency, model identity, language coverage, and explicit exclusions, an agent has everything needed to select and call this tool correctly.

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% and each property (to, from, text, response_format) is documented in-schema with patterns, defaults, and limits, so the baseline is 3. The description adds no parameter-level detail beyond echoing source/target language output, so it neither helps nor hurts.

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+resource ('translate text ... between two languages') and immediately scopes it against non-goals: preserving formatting, certified/legal translation, and speech. A reader can differentiate it from blackwood_audio_transcribe (deferred to for speech) and from the summarize/sentiment siblings without opening any 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?

Explicit 'Use when...' plus 'Do not use for...' exclusions, including a concrete re-routing instruction ('speech (transcribe first)') that names the workflow alternative. This is the when/when-not/alternative pattern done in full.

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

All Blackwood State 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