Skip to main content
Glama
Ichigo3766

PowerPoint MCP Server

by Ichigo3766

create-presentation

Generate a new PowerPoint presentation by specifying its name. Use this tool to initiate the creation process for tailored presentations within 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

  • Handler for the create-presentation tool. Creates a new Presentation object from python-pptx and stores it in the PresentationManager instance.
    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}"
            )
        ]
  • Tool registration in list_tools() decorator, defining the tool's name, description, and input schema.
        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"],
        },
    ),
  • PresentationManager.__init__ method that initializes the dictionary for storing presentations, used by the handler.
    def __init__(self):
        self.presentations: Dict[str, Any] = {}
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 'starts the process of generating,' which implies a write operation, but doesn't disclose behavioral traits like whether it requires specific permissions, what happens if a presentation with the same name exists, if it's idempotent, or what the response includes (e.g., success/failure, file path). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded, consisting of two clear sentences: one stating the purpose and one providing usage guidelines. Every sentence earns its place with no wasted words, making it highly concise and well-structured.

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 tool's complexity as a mutation tool (creating a presentation), with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., permissions, error handling), output format, or how it integrates with sibling tools like 'save-presentation'. For a tool that likely has significant side effects, this is inadequate.

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 parameter 'name' fully documented in the schema as 'Name of the presentation (without .pptx extension)'. The description adds no additional meaning beyond this, as it only references 'the name given by the user' without extra details. With high schema coverage, the baseline is 3, and the description doesn't compensate further.

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 ('powerpoint presentation'), and scope ('with the name given'), though it doesn't explicitly differentiate from sibling tools like 'open-presentation' or 'save-presentation'. The description is more specific than a tautology but lacks sibling differentiation for 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 Guidelines4/5

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

The description provides explicit guidance: 'Use this tool when the user requests to create or generate a new presentation.' This clearly indicates the context for usage. However, it doesn't specify when NOT to use it (e.g., vs. 'open-presentation' for existing presentations) or name alternatives, so it falls short of a perfect score.

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/Ichigo3766/powerpoint-mcp'

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