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

office-powerpoint-mcp-server

Add Slide From Template

add_slide_from_template

Build institutional presentation slides from pre-calculated coordinate templates, including title slides, executive summaries, comparisons, KPI grids, tables, and charts populated with your data.

Instructions

Build institutional presentation slides from pre-calculated coordinate templates.

Supported Templates:

  • title_slide: Authoritative title slide with decorative accent bar and author/date

  • executive_summary: Two structured cards for key observations and recommendations

  • two_column_comparison: Side-by-side comparison cards (current vs target, options A/B)

  • kpi_metrics_grid: 4 high-impact metric cards with big numbers, labels, and YoY trends

  • table_with_commentary: Institutional data table on the left with commentary on the right

  • chart_with_takeaways: Native editable chart on the left with analyst takeaways on the right

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "template_name": "<template_name>",
      "title": "<title>"
    },
    "name": "add_slide_from_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesSlide main title
subtitleNoSlide contextual subtitle
auto_saveNoWhether to automatically save changes to file_path on disk
file_pathNoPath to presentation file within sandbox
slide_indexNoPosition index to insert slide at (appends if None)
color_schemeNoInstitutional color palette nameinstitutional_navy
elements_dataNoData dictionary for template placeholders (cards, metrics, tables, charts)
template_nameYesTemplate ID: title_slide, executive_summary, two_column_comparison, kpi_metrics_grid, table_with_commentary, chart_with_takeaways
presentation_idNoIn-memory presentation ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-idempotent, non-destructive write, so the safety bar is lower. The description adds that layouts are pre-calculated coordinates (no manual positioning needed) and what each template visually renders, but says nothing about the auto_save write to disk, repeated-invocation effects, or failure behavior when elements_data does not match a template.

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 core purpose is front-loaded in one sentence and the catalog is a scannable bulleted list, which is the right shape for six variants. Some entries (decorative accent bar, 'big numbers') are cosmetic filler, but overall there is little waste.

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?

An output schema exists and the schema documents all nine params, so the description needn't restate returns. However, for a template-driven tool the biggest unknown is which elements_data keys each template expects, and the description never says — an agent must guess or call list_templates first.

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 parameter and the template_name enum are already documented, setting the baseline at 3. The description restates template names with visual detail but adds no new meaning about elements_data keys, slide_index semantics, or color_scheme behavior beyond the enum.

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 first line gives a specific verb, resource and method: 'Build institutional presentation slides from pre-calculated coordinate templates', and the catalog of six template names makes the scope concrete. It does not explicitly distinguish itself from sibling adders like add_bullet_slide, though 'from template' implies a contrast.

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 template descriptions imply when each variant applies (comparison cards for 'current vs target', chart_with_takeaways for chart-plus-commentary), which is real but indirect guidance. There is no explicit when-to-use vs add_bullet_slide/manage_slides, no statement of prerequisites, and no guidance on file_path vs presentation_id.

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