Skip to main content
Glama

create-presentation

Generate a new PowerPoint presentation by specifying a name. This tool initiates presentation creation for the PowerPoint MCP Server.

Instructions

This tool starts the process of generating a new powerpoint presentation with the name given by the user. Use this tool when the user requests to create or generate a new presentation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the presentation (without .pptx extension)

Implementation Reference

  • The handler for the 'create-presentation' tool. It creates a new empty PowerPoint presentation instance using the pptx library and stores it in the PresentationManager's presentations dictionary for subsequent slide additions.
    elif name == "create-presentation":
    
        presentation_name = arguments.get("name")
        if not presentation_name:
            raise ValueError("Missing presentation name")
    
        # Create new presentation
        prs = Presentation()
        try:
            presentation_manager.presentations[presentation_name] = prs
        except KeyError as e:
            raise ValueError(f"Unable to add {presentation_name} to presentation. Error: {str(e)}")
    
        return [
            types.TextContent(
                type="text",
                text=f"Created new presentation: {presentation_name}"
            )
        ]
  • Registers the 'create-presentation' tool in the list_tools handler, including its name, description, and input schema which requires a 'name' parameter.
    types.Tool(
        name="create-presentation",
        description="This tool starts the process of generating a new powerpoint presentation with the name given "
                    "by the user. Use this tool when the user requests to create or generate a new presentation.",
        inputSchema={
            "type": "object",
            "properties": {
                "name": {
                    "type": "string",
                    "description": "Name of the presentation (without .pptx extension)",
                },
            },
            "required": ["name"],
        },
    ),
  • Defines the input schema for the 'create-presentation' tool, specifying an object with a required 'name' string property.
        inputSchema={
            "type": "object",
            "properties": {
                "name": {
                    "type": "string",
                    "description": "Name of the presentation (without .pptx extension)",
                },
            },
            "required": ["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 of behavioral disclosure. It mentions 'starts the process of generating,' which implies a creation operation but doesn't clarify what 'starts' entails (e.g., whether it creates a file immediately, requires saving later, or has side effects). It lacks details on permissions, error handling, or what happens after generation, leaving significant gaps for a mutation 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 concise and front-loaded, consisting of two sentences that directly address purpose and usage. There's no wasted text, and it efficiently communicates the core information. However, it could be slightly more structured by separating purpose and guidelines more clearly, preventing a perfect score.

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 a presentation creation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., a presentation object, success status), potential errors, or how it interacts with sibling tools like 'save-presentation'. For a mutation tool, this leaves too many unknowns for effective agent use.

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?

The schema description coverage is 100%, with the 'name' parameter fully documented in the input schema. The description adds minimal value beyond the schema by mentioning 'name given by the user' but doesn't provide additional context like naming conventions or constraints. This meets the baseline of 3 since the schema handles most of the parameter documentation.

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: 'starts the process of generating a new powerpoint presentation with the name given by the user.' It specifies the verb ('starts generating'), resource ('new powerpoint presentation'), and key input ('name given by the user'). However, it doesn't explicitly differentiate from sibling tools like 'open-presentation' or 'save-presentation', which prevents a perfect score.

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 some usage guidance: 'Use this tool when the user requests to create or generate a new presentation.' This implies the context but doesn't explicitly state when NOT to use it or mention alternatives like 'open-presentation' for existing presentations. The guidance is helpful but lacks specificity about exclusions or comparisons to siblings.

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