Skip to main content
Glama
supercurses

Powerpoint MCP Server

by supercurses

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"],
    },

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
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 the tool opens and saves a copy for backup, implying a read operation with a side effect, but doesn't disclose critical behavioral traits like whether it requires specific permissions, if the original presentation is modified, error handling, or rate limits. This leaves significant gaps for a tool with potential mutation implications.

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 with two sentences that are front-loaded: the first states the core action, and the second provides usage context. There's no wasted text, but it could be slightly more structured by separating purpose and guidelines more clearly.

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?

Given the complexity of opening and saving a presentation with no annotations and no output schema, the description is incomplete. It doesn't explain what 'opens' entails (e.g., loads for editing, read-only view), the backup process details, or return values, leaving the agent with insufficient context for safe invocation.

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 ('presentation_name' and 'output_path'). The description adds minimal value beyond the schema by implying the 'output_path' is for backup, but doesn't provide additional semantics like format examples or constraints. Baseline 3 is appropriate as 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 with specific verbs ('opens an existing presentation' and 'saves a copy to a new file for backup'), distinguishing it from sibling tools like 'create-presentation' and 'save-presentation'. However, it doesn't explicitly differentiate from all siblings, such as 'add-slide-*' tools, which is why it's not a perfect 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?

The description provides implied usage guidance by stating 'Use this tool when the user requests to open a presentation that has already been created,' which helps distinguish it from 'create-presentation'. However, it lacks explicit alternatives (e.g., when to use 'save-presentation' instead) and doesn't mention when not to use it, such as for editing without backup.

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