Skip to main content
Glama

add-slide-section-header

Add a section header slide to organize PowerPoint presentations into clear segments with titles and optional subtitles.

Instructions

This tool adds a section header (a.k.a segue) slide to the presentation you are working on. The tool doesn't return anything. It requires the presentation_name to work on.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
presentation_nameYesName of the presentation to add the slide to
headerYesSection header title
subtitleNoSection header subtitle

Implementation Reference

  • The core handler function that adds a section header slide to the presentation. It retrieves the presentation, uses slide layout 2 (SLIDE_LAYOUT_SECTION_HEADER), sets the header as title, and optional subtitle.
    def add_section_header_slide(self, presentation_name: str, header: str, subtitle: str):
        """
        Create a section header slide for the given presentation
    
        Args:
            presentation_name: The presentation to add the slide to
            header: The section header to use
            subtitle: The subtitle of the section header to use
        """
        try:
            prs = self.presentations[presentation_name]
        except KeyError as e:
            raise ValueError(f"Presentation '{presentation_name}' not found")
        slide_master = prs.slide_master
    
        # Add a new slide with layout
        slide_layout = prs.slide_layouts[self.SLIDE_LAYOUT_SECTION_HEADER]
        slide = prs.slides.add_slide(slide_layout)
    
        # Set the subtitle
        if subtitle:
            subtitle_shape = slide.placeholders[1]
            text_frame = subtitle_shape.text_frame
            text_frame.text = subtitle
    
        # Set the section header
        if header:
            header_shape = slide.shapes.title
            header_shape.text = header
    
        return slide
  • Tool registration in the list_tools handler, including name, description, and input schema.
    types.Tool(
        name="add-slide-section-header",
        description="This tool adds a section header (a.k.a segue) slide to the presentation you are working on. The tool doesn't "
                    "return anything. It requires the presentation_name to work on.",
        inputSchema={
            "type": "object",
            "properties": {
                "presentation_name": {
                    "type": "string",
                    "description": "Name of the presentation to add the slide to",
                },
                "header": {
                    "type": "string",
                    "description": "Section header title",
                },
                "subtitle": {
                    "type": "string",
                    "description": "Section header subtitle",
                }
    
            },
            "required": ["presentation_name", "header"],
        },
    ),
  • Dispatch handler in call_tool that validates arguments and delegates to PresentationManager.add_section_header_slide.
    elif name == "add-slide-section-header":
        presentation_name = arguments.get("presentation_name")
        header = arguments.get("header")
        subtitle = arguments.get("subtitle")
    
        if not all([presentation_name, header]):
            raise ValueError("Missing required arguments")
    
        if presentation_name not in presentation_manager.presentations:
            raise ValueError(f"Presentation not found: {presentation_name}")
    
        try:
            slide = presentation_manager.add_section_header_slide(presentation_name, header, subtitle)
        except Exception as e:
            raise ValueError(f"Unable to add slide '{header}' to presentation: {presentation_name}")
    
        return [
            types.TextContent(
                type="text",
                text=f"Added slide '{header}' to presentation: {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 of behavioral disclosure. It states 'The tool doesn't return anything', which is useful, but lacks details on side effects (e.g., whether it modifies an existing presentation in-place), error handling, or permissions needed. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 directly address the tool's action and a key requirement. It avoids unnecessary words, though it could be slightly more structured by front-loading the core purpose more explicitly.

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 (adding a slide with specific content), no annotations, no output schema, and 100% schema coverage, the description is minimally adequate. It covers the basic purpose and a behavioral note about no return value, but lacks details on usage context, error cases, or integration with sibling tools, leaving room for improvement.

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 all three parameters (presentation_name, header, subtitle) with clear descriptions. The description adds no additional meaning beyond the schema, such as examples or constraints, but doesn't need to compensate for gaps. Baseline 3 is appropriate when the schema handles parameter documentation adequately.

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 verb ('adds') and resource ('a section header slide to the presentation you are working on'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'add-slide-title-only' or 'add-slide-title-content', which also add slides but with different content types.

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 provides no guidance on when to use this tool versus alternatives, such as when a section header is needed versus other slide types like title slides or comparison slides. It mentions that it 'requires the presentation_name to work on', but this is a basic requirement rather than contextual usage advice.

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