Skip to main content
Glama

Translate & Adapt Scene to Bangla

fahi_translate_and_adapt_scene
Read-onlyIdempotent

[100% FREE — Zero API Key Needed] Convert an English scene summary or draft Bengali line into an authentic Dhaka-standard Bangladeshi Bengali voiceover script with a Romanized Banglish phonetic reading guide.

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": {
      "englishSummary": "<englishSummary>"
    },
    "name": "fahi_translate_and_adapt_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNoTarget voiceover tone.commercial
onScreenTextNoVisible on-screen text or overlay caption.
currentBanglaNoExisting Bengali draft to refine or tone-adapt.
englishSummaryYesEnglish visual description or summary of the video scene.

Output Schema

NameRequiredDescriptionDefault
engineNoLocalization engine used.
banglaScriptYesAdapted Bangladeshi Bengali voiceover script.
phoneticGuideYesRomanized Banglish phonetic reading guide.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / englishSummary / minLength
      Added value: +1
    • addedInput schema / properties / tone / default
      Added value: +"commercial"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "banglaScript": {
      +      "description": "Adapted Bangladeshi Bengali voiceover script.",
      +      "type": "string"
      +    },
      +    "engine": {
      +      "description": "Localization engine used.",
      +      "type": "string"
      +    },
      +    "phoneticGuide": {
      +      "description": "Romanized Banglish phonetic reading guide.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "banglaScript",
      +    "phoneticGuide"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower, and the description still adds real context: the target dialect standard (Dhaka), the output artifact (voiceover script plus phonetic guide), and the absence of an API key requirement. It does not describe how the two input modes interact or any length or rate constraints, which is the main remaining 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?

A single sentence that front-loads the offer and then the concrete transformation, with no filler clauses. The bracketed '[100% FREE — Zero API Key Needed]' prefix is marketing framing rather than functional information, which costs a point on tightness but does convey an access constraint an agent might care about.

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?

With an output schema present, the description need not explain return values, and annotations plus a fully documented four-parameter schema cover the rest. The description is complete enough to call the tool correctly for the common case, with only the multi-input interaction and tone behavior left implicit.

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 every parameter carries its own description, so the schema does the heavy lifting and a baseline of 3 applies. The description does add a little meaning by framing englishSummary and currentBangla as alternative starting points (source summary versus existing draft to refine), but it never explains precedence when both are supplied or what the tone enum changes.

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 uses a specific verb-plus-resource formulation: convert an English scene summary or a draft Bengali line into a Dhaka-standard Bangladeshi Bengali voiceover script, and it names the distinctive deliverable (a Romanized Banglish phonetic reading guide). That is far more than a restatement of the tool name and lets an agent tell it apart from a plain TTS generator. It stops short of explicitly contrasting itself with siblings such as fahi_generate_bangla_tts.

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?

Usage is only implied: the phrasing 'an English scene summary or draft Bengali line' signals two entry paths, which loosely maps to the englishSummary versus currentBangla parameters. There is no explicit statement of when to choose this over fahi_generate_bangla_tts, no prerequisites, and no guidance on tone selection. Adequate but with clear gaps.

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.