Skip to main content
Glama
office-powerpoint-mcp-server

office-powerpoint-mcp-server

Format Master Footer

format_master_footer

Adds a themed divider line, slide numbers, confidentiality notice, and date across slides for consistent institutional footers.

Instructions

Add institutional divider line, slide numbering, confidentiality notice, and date across slides.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "format_master_footer"
  }
}

Input Schema

NameRequiredDescriptionDefault
themeNoColor scheme for footer accentsinstitutional_navy
auto_saveNoWhether to automatically save changes to file_path on disk
date_textNoExplicit date string override (e.g. 'November 2026')
file_pathNoPath to presentation file within sandbox
footer_textNoConfidentiality or disclaimer text on bottom-leftConfidential - For Internal Use Only
include_dateNoWhether to include current month/year in footer
presentation_idNoIn-memory presentation ID
skip_title_slideNoWhether to skip adding footer to slide 0
include_slide_numbersNoWhether to include 'Slide X of Y' on bottom-right

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare this is a non-read-only, non-idempotent mutation, yet the description says nothing about the consequence — repeated calls may stack duplicate footer elements on the same slides. It also omits that auto_save defaults to true and writes to disk at file_path, and whether pre-existing footer content is replaced or appended, which is critical for a collection-wide formatting mutation.

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?

A single front-loaded sentence that lists the concrete outputs with no filler or redundancy. It is efficiently sized, though the compressed list form leaves out the operational context an agent would need.

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?

The tool has an output schema and fully documented parameters, so return values and option meaning need not be restated. However, for a nine-parameter, non-idempotent, disk-writing formatting mutation, the description omits persistence behavior and repeat-invocation effects — the main open risks.

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 every one of the nine parameters is already documented, establishing a baseline of 3. The description reinforces a few of them (slide numbering, confidentiality text, date) but adds no meaning for theme, auto_save, file_path, presentation_id, or skip_title_slide beyond what the schema states.

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 names a concrete verb ("Add") and enumerates the specific artifacts applied (divider line, slide numbering, confidentiality notice, date) plus scope ("across slides"), so the operation is immediately recognizable. It does not distinguish itself from near-siblings such as apply_theme or manage_slides, and it leaves ambiguous whether this targets a master/layout or every individual slide.

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?

There is no guidance on when to choose this over apply_theme or manage_slides, no indication of whether footers should be applied once per presentation, and no note on choosing presentation_id (in-memory) versus file_path (on-disk). The agent is left to infer all selection criteria from the schema alone.

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