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

office-powerpoint-mcp-server

Add Data Table

add_data_table

Create styled data tables on PowerPoint slides with automatic column widths, theme-based headers, zebra rows, numeric alignment, and optional source footnotes for publication-ready reporting.

Instructions

Create a publication-ready institutional data table on a slide.

Features:

  • Automatic column width calculation with wider category/label column 0

  • Institutional styled header with theme primary background (#1B365D) and bold white text

  • Alternating row zebra striping with slate gray fill (#F1F5F9)

  • Subtle OpenXML horizontal bottom borders (#CBD5E1) on every row

  • Intelligent alignment: Left-aligned for text/labels, Right-aligned for numeric data

  • Clean cell margins / padding and optional source footnote

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": {
      "slide_index": "<slide_index>",
      "headers": "<headers>",
      "rows": "<rows>"
    },
    "name": "add_data_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoTop coordinate in inches
leftNoLeft coordinate in inches
rowsYes2D array of row cell data
themeNoColor scheme to use for table stylinginstitutional_navy
widthNoTotal table width in inches
heightNoTotal table height in inches (auto-calculated if None)
headersYesList of column header labels
footnoteNoOptional source or disclaimer note under the table
auto_saveNoWhether to automatically save changes to file_path on disk
file_pathNoPath to presentation file within sandbox
slide_indexYes0-based index of slide to add table to
column_widthsNoExplicit column widths in inches (auto-calculated if None)
presentation_idNoIn-memory presentation ID
highlight_first_columnNoWhether to style first column with bold font

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the mutation profile is partially covered, and the description adds real value about the visual result (zebra striping, alignment rules, footnote). It omits the operational side of the mutation: how auto_save interacts with file_path, what happens when both presentation_id and file_path are null, or whether an out-of-range slide_index fails or is clamped. Good on appearance, thin on side effects and failure modes.

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?

Superb structure for a formatting-heavy tool: a single lead sentence naming the outcome, then a scannable feature list. It ends exactly where the visual contract ends, and nothing in it is padding.

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?

With 14 parameters, an output schema, and full schema coverage, the definition covers visual behavior well. It falls short on the surrounding context an agent needs before calling: how the tool behaves when neither presentation_id nor file_path is supplied, whether a footnote reserves layout space, and what the success output represents.

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% and each of the 14 parameters is documented inline, so the baseline is 3. The 'wider category/label column 0' and 'bold first column' notes loosely tie back to column_widths and highlight_first_column but add no syntax, format, or unit guidance beyond what the schema already supplies.

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?

States a specific verb and resource ('Create a ... data table on a slide') with a clear scope (slide-targeted table creation), which is enough to separate it from siblings like add_image or add_native_chart. It never names the closest alternative, update_table_cells, so the reader has to infer that this tool is for new tables only.

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 is entirely a feature list of visual results; it says nothing about when to use this tool versus update_table_cells (for existing tables) or the other add_* content tools. There are no prerequisites stated either (whether presentation_id or file_path must already resolve to an open deck, and what happens on a bad slide_index is left unstated).

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