PowerPoint Translator

translate_specific_slides

Translate chosen slides in a PowerPoint presentation while preserving formatting. Specify slide numbers to translate only those pages, leaving the rest untouched.

Instructions

Translate specific slides in a PowerPoint presentation.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`dry_run`	No
`model_id`	No	Amazon Bedrock Mantle model ID to use for translation	openai.gpt-5.6-terra
`input_file`	Yes	Path to the input PowerPoint file (.pptx)
`output_file`	No	Path to save the translated file (optional, auto-generated if not provided)
`cache_backend`	No		sqlite
`glossary_file`	No
`slide_numbers`	Yes	Comma-separated slide numbers to translate (e.g., "1,3,5" or "2-4,7")
`slide_workers`	No	Maximum parallel workers within this presentation
`source_language`	No
`target_language`	No	Target language code (e.g., 'ko', 'ja', 'es', 'fr', 'de')	ja
`enable_polishing`	No	Enable natural language polishing for more fluent translation
`translate_charts`	No
`slides_per_worker`	No	Number of slides assigned to each worker
`auto_detect_source`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed25 schema fields changedv1.1.0Aug 24, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / auto_detect_source

Added value: +{
+  "default": true,
+  "type": "boolean"
+}

addedInput schema / properties / cache_backend

Added value: +{
+  "default": "sqlite",
+  "type": "string"
+}

addedInput schema / properties / dry_run

Added value: +{
+  "default": false,
+  "type": "boolean"
+}

addedInput schema / properties / enable_polishing / description

Added value: +"Enable natural language polishing for more fluent translation"

removedInput schema / properties / enable_polishing / title
```
Removed value: -"Enable Polishing"
```

addedInput schema / properties / glossary_file

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / input_file / description

Added value: +"Path to the input PowerPoint file (.pptx)"

removedInput schema / properties / input_file / title
```
Removed value: -"Input File"
```

changedInput schema / properties / model_id / default

Previous value: -"us.anthropic.claude-3-7-sonnet-20250219-v1:0"New value: +"openai.gpt-5.6-terra"

addedInput schema / properties / model_id / description

Added value: +"Amazon Bedrock Mantle model ID to use for translation"

removedInput schema / properties / model_id / title
```
Removed value: -"Model Id"
```

addedInput schema / properties / output_file / description

Added value: +"Path to save the translated file (optional, auto-generated if not provided)"

removedInput schema / properties / output_file / title
```
Removed value: -"Output File"
```

addedInput schema / properties / slide_numbers / description

Added value: +"Comma-separated slide numbers to translate (e.g., \"1,3,5\" or \"2-4,7\")"

removedInput schema / properties / slide_numbers / title
```
Removed value: -"Slide Numbers"
```

addedInput schema / properties / slide_workers

Added value: +{
+  "default": 4,
+  "description": "Maximum parallel workers within this presentation",
+  "type": "integer"
+}

addedInput schema / properties / slides_per_worker

Added value: +{
+  "default": 30,
+  "description": "Number of slides assigned to each worker",
+  "type": "integer"
+}

addedInput schema / properties / source_language

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

changedInput schema / properties / target_language / default
```
Previous value: -"ko"New value: +"ja"
```

addedInput schema / properties / target_language / description

Added value: +"Target language code (e.g., 'ko', 'ja', 'es', 'fr', 'de')"

removedInput schema / properties / target_language / title
```
Removed value: -"Target Language"
```

addedInput schema / properties / translate_charts

Added value: +{
+  "default": true,
+  "type": "boolean"
+}

removedOutput schema / properties / result / title
```
Removed value: -"Result"
```
removedOutput schema / title
```
Removed value: -"_WrappedResult"
```

First observedv1.0.0Aug 15, 2025

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are present, so the description carries the full burden of transparent behavior. It only says 'translate' and provides no insight into whether the original file is modified, how output files are produced, whether dry-run is available, or what model/language behavior is involved. This is minimal behavior disclosure for a complex tool.

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?

The description is a single, concise sentence with no filler. It is front-loaded with the core action, though it is so terse that it may sacrifice usefulness for brevity.

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

Completeness2/5

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

The tool has 14 parameters and several closely related sibling tools, yet the description provides only the basic action. It does not clarify whether slides are selected via `slide_numbers`, whether a new file is generated, what happens with missing glossaries or charts, and how this differs from batch or whole-presentation variants. The output schema helps but does not compensate for this lack of contextual 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 descriptions are present for 8 of 14 parameters (57%), and several defaults and parameter names are self-explanatory. The description adds essentially no parameter-specific meaning beyond the schema, though it does reinforce the slide-subset intent behind the `slide_numbers` parameter.

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 names a specific action ('Translate specific slides') and the target resource ('a PowerPoint presentation'), clearly conveying that only a subset of slides will be handled rather than an entire deck. It lacks an explicit contrast with sibling tools, but the scope is reasonably unambiguous.

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 phrase 'specific slides' implies that this tool is for translating selected slides rather than a whole presentation, giving some usage context. However, there is no explicit statement of when to prefer this tool over `translate_powerpoint` or `batch_translate_powerpoint`, nor any exclusion or alternative guidance.

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

Deploy Server