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

office-powerpoint-mcp-server

Apply Theme

apply_theme

Apply a consistent institutional color palette and typography across PowerPoint slides, tables, and cards to standardize presentation styling in one step.

Instructions

Apply institutional color palette and typography across slides, tables, and cards.

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": "apply_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
auto_saveNoWhether to automatically save changes to file_path on disk
file_pathNoPath to presentation file within sandbox
theme_nameNoTheme palette: institutional_navy, modern_blue, corporate_gray, elegant_green, warm_redinstitutional_navy
slide_indexNoSpecific 0-based slide index (applies to all slides if None)
presentation_idNoIn-memory presentation ID
apply_backgroundNoWhether to apply theme background color via OpenXML

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is largely covered. The description usefully adds the blast radius (slides, tables, and cards get restyled), but omits the significant side effect that auto_save defaults to true and will write changes to file_path on disk, which is exactly the kind of behavior the annotations don't convey.

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 well-formed sentence with no filler or redundancy; the affected surfaces are front-loaded. It is efficient but sits at the lower bound of sufficiency for a six-parameter mutating tool.

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?

This is a mutating tool with a persistence side effect (auto_save defaulting to true), dual targeting via file_path or presentation_id, and optional per-slide scoping, none of which the description addresses. The output schema and annotations offload some burden, but an agent could easily mis-scope or unintentionally overwrite a file based on this description alone.

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 all six parameters are already documented in-schema, setting the baseline at 3. The description adds no meaning beyond 'theme' — it doesn't explain the in-memory presentation_id vs. on-disk file_path modes, the slide_index scoping, or the apply_background flag.

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 uses a specific verb ('Apply') plus concrete resources ('institutional color palette and typography') and names the affected surfaces (slides, tables, cards), which is well beyond tautology. It loses a point because it doesn't distinguish this from siblings like format_master_footer or manage_text, and 'institutional' undersells that five distinct palettes are selectable.

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 statement of when to use this vs. alternatives, no prerequisite (e.g., must a presentation exist in memory or a file be loaded first), and no guidance on interactive formatting tools vs. this blanket re-theme. The only implied usage is 'you want a theme applied.'

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