Skip to main content
Glama

open-presentation

Open existing PowerPoint presentations and create backup copies to preserve original files while editing. This tool helps users work on presentations without risking data loss.

Instructions

Opens an existing presentation and saves a copy to a new file for backup. Use this tool when the user requests to open a presentation that has already been created.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
presentation_nameYesName of the presentation to open
output_pathNoPath where to save the presentation (optional)

Implementation Reference

  • Handler logic within the call_tool function that executes the 'open-presentation' tool: validates input, sanitizes file path, loads the PPTX presentation using python-pptx, creates a backup copy, stores the presentation object in PresentationManager, and returns a success message.
    if name == "open-presentation":
        presentation_name = arguments.get("presentation_name")
        if not presentation_name:
            raise ValueError("Missing presentation name")
        file_name = f"{presentation_name}.pptx"
    
        try:
            safe_file_path = sanitize_path(folder_path, file_name)
        except ValueError as e:
            raise ValueError(f"Invalid file path: {str(e)}")
    
        # attempt to load presentation
        try:
            prs = Presentation(safe_file_path)
        except Exception as e:
            raise ValueError(f"Unable to load {safe_file_path}. Error: {str(e)}")
    
        # Create a backup of the original file
        file_name = BACKUP_FILE_NAME
        try:
            safe_file_path = sanitize_path(folder_path, file_name)
        except ValueError as e:
            raise ValueError(f"Invalid file path: {str(e)}")
        # attempt to save a backup of presentation
        try:
            prs.save(safe_file_path)
        except Exception as e:
            raise ValueError(f"Unable to save {safe_file_path}. Error: {str(e)}")
    
        presentation_manager.presentations[presentation_name] = prs
    
        return [
            types.TextContent(
                type="text",
                text=f"Opened presentation: {presentation_name}"
            )
        ]
  • Registration of the 'open-presentation' tool in the list_tools() handler, including its name, description, and input schema definition.
    types.Tool(
        name="open-presentation",
        description="Opens an existing presentation and saves a copy to a new file for backup. Use this tool when "
                    "the user requests to open a presentation that has already been created.",
        inputSchema={
            "type": "object",
            "properties": {
                "presentation_name": {
                    "type": "string",
                    "description": "Name of the presentation to open",
                },
                "output_path": {
                    "type": "string",
                    "description": "Path where to save the presentation (optional)",
                },
            },
            "required": ["presentation_name"],
        },
    ),
  • Input schema definition for the 'open-presentation' tool, specifying required 'presentation_name' and optional 'output_path'.
    inputSchema={
        "type": "object",
        "properties": {
            "presentation_name": {
                "type": "string",
                "description": "Name of the presentation to open",
            },
            "output_path": {
                "type": "string",
                "description": "Path where to save the presentation (optional)",
            },
        },
        "required": ["presentation_name"],
    },
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. It mentions saving a copy for backup, which implies non-destructive behavior, but doesn't disclose other traits like whether it requires specific permissions, what happens if the presentation doesn't exist, or if there are rate limits. For a tool with mutation implications (saving a copy) and zero annotation coverage, this is inadequate.

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 appropriately sized with two sentences: the first states the purpose, and the second provides usage guidelines. It's front-loaded with the core functionality. However, the second sentence could be slightly more concise (e.g., 'Use when opening an existing presentation').

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 moderate complexity (opening and saving a copy), no annotations, no output schema, and 100% schema coverage, the description is minimally adequate. It covers purpose and usage but lacks behavioral details (e.g., error handling, backup specifics) and output information, leaving gaps for an agent to operate effectively.

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 the schema already documents both parameters fully. The description adds no additional meaning beyond what the schema provides (e.g., it doesn't explain the backup purpose in relation to parameters). Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the tool's purpose: 'Opens an existing presentation and saves a copy to a new file for backup.' This specifies the verb (open and save copy) and resource (presentation), distinguishing it from siblings like 'create-presentation' or 'save-presentation'. However, it doesn't explicitly differentiate from 'save-presentation' in terms of backup vs. regular save.

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

Usage Guidelines4/5

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

The description provides clear context for when to use it: 'Use this tool when the user requests to open a presentation that has already been created.' This distinguishes it from 'create-presentation' for new presentations. However, it doesn't specify when NOT to use it (e.g., vs. 'save-presentation' for saving without opening) or mention alternatives explicitly.

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

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/supercurses/powerpoint'

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