Skip to main content
Glama

lunara_translate

Idempotent

Translate the text of an existing job’s cues into another language. Every cue boundary and timestamp is preserved; only the text changes. Use this instead of translating yourself so the timing contract holds.

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": {
      "jobId": "<jobId>",
      "targetLang": "<targetLang>"
    },
    "name": "lunara_translate"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesThe job whose cues to translate.
trackNoWhich track to read. Default primary.
targetLangYesTarget language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / targetLang / enum
      Previous value: -[
      -  "zh-Hant",
      -  "zh-Hans",
      -  "yue-Hant",
      -  "en",
      -  "ja",
      -  "ko",
      -  "es",
      -  "fr",
      -  "de",
      -  "it",
      -  "pt",
      -  "pt-BR",
      -  "nl",
      -  "sv",
      -  "da",
      -  "no",
      -  "fi",
      -  "pl",
      -  "cs",
      -  "sk",
      -  "hu",
      -  "ro",
      -  "hr",
      -  "sl",
      -  "et",
      -  "lv",
      -  "lt",
      -  "ru",
      -  "uk",
      -  "bg",
      -  "sr",
      -  "ar",
      -  "he",
      -  "fa",
      -  "tr",
      -  "hi",
      -  "th",
      -  "vi",
      -  "id",
      -  "ms",
      -  "tl",
      -  "el",
      -  "sw"
      -]New value: +[
      +  "zh-Hant",
      +  "zh-CN",
      +  "yue-Hant",
      +  "en",
      +  "ja",
      +  "ko",
      +  "es",
      +  "fr",
      +  "de",
      +  "it",
      +  "pt",
      +  "pt-BR",
      +  "nl",
      +  "sv",
      +  "da",
      +  "no",
      +  "fi",
      +  "pl",
      +  "cs",
      +  "sk",
      +  "hu",
      +  "ro",
      +  "hr",
      +  "sl",
      +  "et",
      +  "lv",
      +  "lt",
      +  "ru",
      +  "uk",
      +  "bg",
      +  "sr",
      +  "ar",
      +  "he",
      +  "fa",
      +  "tr",
      +  "hi",
      +  "th",
      +  "vi",
      +  "id",
      +  "ms",
      +  "tl",
      +  "el",
      +  "sw"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / targetLang / enum
      Previous value: -[
      -  "zh-Hant",
      -  "en",
      -  "ja",
      -  "ko",
      -  "es",
      -  "fr",
      -  "de"
      -]New value: +[
      +  "zh-Hant",
      +  "zh-Hans",
      +  "yue-Hant",
      +  "en",
      +  "ja",
      +  "ko",
      +  "es",
      +  "fr",
      +  "de",
      +  "it",
      +  "pt",
      +  "pt-BR",
      +  "nl",
      +  "sv",
      +  "da",
      +  "no",
      +  "fi",
      +  "pl",
      +  "cs",
      +  "sk",
      +  "hu",
      +  "ro",
      +  "hr",
      +  "sl",
      +  "et",
      +  "lv",
      +  "lt",
      +  "ru",
      +  "uk",
      +  "bg",
      +  "sr",
      +  "ar",
      +  "he",
      +  "fa",
      +  "tr",
      +  "hi",
      +  "th",
      +  "vi",
      +  "id",
      +  "ms",
      +  "tl",
      +  "el",
      +  "sw"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / targetLang / enum
      Previous value: -[
      -  "zh-Hant",
      -  "en",
      -  "ja",
      -  "ko"
      -]New value: +[
      +  "zh-Hant",
      +  "en",
      +  "ja",
      +  "ko",
      +  "es",
      +  "fr",
      +  "de"
      +]
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the write/idempotent/safe profile is known. The description adds real behavioral value that annotations cannot convey: cue boundaries and timestamps are preserved and only text changes. It still omits whether an existing target track is overwritten and whether the operation is synchronous.

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?

Three short sentences, front-loaded with the action and scope, then the preservation guarantee, then the reason to use it. Every sentence carries distinct information with no redundant restatement of the name.

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?

For a three-parameter tool with full schema coverage and informative annotations, the description covers purpose, scope, and preservation guarantees. Without an output schema, it does not tell the agent what comes back or whether existing target-language text is replaced, which is a minor but real gap.

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 jobId, track, and targetLang are already documented, and the description adds only that the translation targets "another language." The meaning of track and the language enum are left entirely to the schema, which is adequate but adds no surplus meaning.

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

Purpose4/5

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

The description gives a specific verb and resource: "Translate the text of an existing job's cues into another language," plus a scope constraint that only text changes while timing is preserved. It does not explicitly distinguish itself from plausible siblings such as lunara_rewrite, so it stops short of a 5.

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?

"Use this instead of translating yourself so the timing contract holds" gives a clear reason to prefer the tool over a DIY approach, and "an existing job's cues" implies the job must already exist. However, there is no guidance on prerequisites (e.g., must the job be transcribed first?) or on when to use a sibling instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources