Skip to main content
Glama
daekeun-ml

PowerPoint Translator

by daekeun-ml

get_translation_help

Access helpful guidance and usage examples for translating PowerPoint presentations with formatting intact. Learn how to effectively use the translation features for your slides.

Instructions

Get help information about using the PowerPoint translator.

Returns: Help text with usage examples

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function for the 'get_translation_help' MCP tool. Decorated with @mcp.tool() for registration. Returns a detailed help message with usage instructions and examples for all available tools.
    @mcp.tool()
    def get_translation_help() -> str:
        """
        Get help information about using the PowerPoint translator.
        
        Returns:
            Help text with usage examples
        """
        return """📖 PowerPoint Translator Help
    
    🎯 Main Functions:
    • translate_powerpoint() - Translate entire PowerPoint presentation
    • translate_specific_slides() - Translate only specific slides
    • get_slide_info() - Get presentation overview and slide previews
    • get_slide_preview() - Get detailed preview of a specific slide
    
    📋 Required Parameters:
    • input_file: Path to your .pptx file
    
    🔧 Optional Parameters:
    • target_language: Language code (default: 'ko' for Korean)
    • output_file: Output path (auto-generated if not specified)
    • model_id: Bedrock model (default: Claude 3.7 Sonnet)
    • enable_polishing: Natural translation vs literal (default: true)
    
    💡 Usage Examples:
    
    1. Get presentation information:
       get_slide_info("presentation.pptx")
    
    2. Preview specific slide:
       get_slide_preview("presentation.pptx", 3)
    
    3. Translate entire presentation:
       translate_powerpoint("presentation.pptx")
    
    4. Translate specific slides (individual):
       translate_specific_slides("slides.pptx", "1,3,5")
    
    5. Translate slide range:
       translate_specific_slides("slides.pptx", "2-4")
    
    6. Translate mixed (individual + range):
       translate_specific_slides("slides.pptx", "1,3-5,8")
    
    7. Translate to Spanish with custom output:
       translate_specific_slides("slides.pptx", "1-3", "es", "spanish_slides.pptx")
    
    8. Literal translation (no polishing):
       translate_specific_slides("doc.pptx", "2,4", "ja", enable_polishing=False)
    
    🌐 Get supported languages:
       list_supported_languages()
    
    🤖 Get supported models:
       list_supported_models()
    
    ⚙️ Configuration:
    • AWS credentials must be configured (aws configure)
    • Bedrock access required in your AWS account
    • Supported file format: .pptx only
    
    📄 Slide Number Format:
    • Individual slides: "1,3,5"
    • Ranges: "2-4" (translates slides 2, 3, 4)
    • Mixed: "1,3-5,8" (translates slides 1, 3, 4, 5, 8)"""
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions that the tool 'Returns help text with usage examples,' which indicates a read-only, informational operation. However, it does not disclose other behavioral traits such as error conditions, rate limits, or authentication needs, which are important for a tool in a PowerPoint translation context.

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 concise and front-loaded, consisting of two sentences that directly state the purpose and return value. There is no wasted text, and it efficiently conveys the essential information without unnecessary details.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no annotations) and the presence of an output schema, the description is somewhat complete but lacks depth. It explains the return value ('help text with usage examples'), but does not provide context on what the help entails or how it integrates with sibling tools, leaving gaps in understanding the tool's role in the broader system.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and the schema description coverage is 100%, so there are no parameters to document. The description does not add parameter semantics beyond the schema, but this is acceptable given the lack of parameters. A baseline score of 4 is appropriate as it compensates for the simplicity of the tool.

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

Purpose3/5

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

The description states the tool 'Get help information about using the PowerPoint translator,' which provides a clear verb ('Get help information') and resource ('PowerPoint translator'). However, it does not distinguish this from potential sibling tools like 'list_supported_languages' or 'list_supported_models,' which might also provide informational content, making the purpose somewhat vague in context.

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

Usage Guidelines2/5

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

The description offers no guidance on when to use this tool versus alternatives. It does not mention prerequisites, context for usage, or exclusions, leaving the agent to infer usage based on the tool name alone. This lack of explicit guidance reduces its effectiveness in tool selection.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/daekeun-ml/ppt-translator'

If you have feedback or need assistance with the MCP directory API, please join our Discord server