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

office-powerpoint-mcp-server

Add Native Chart

add_native_chart

Create native, editable PowerPoint charts with custom categories, series data, chart types, legends, gridlines, and data labels to add visual data directly to slides.

Instructions

Create a native, editable PowerPoint chart.

Supports COLUMN_CLUSTERED, LINE, PIE, and BAR_CLUSTERED charts with custom series data, legend positioning, gridline toggling, and data labels.

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>",
      "chart_type": "<chart_type>",
      "categories": "<categories>",
      "series": "<series>"
    },
    "name": "add_native_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoTop coordinate in inches
leftNoLeft coordinate in inches
titleNoOptional chart header title
widthNoChart width in inches
heightNoChart height in inches
seriesYesList of data series with series name and numerical values
auto_saveNoWhether to automatically save changes to file_path on disk
file_pathNoPath to presentation file within sandbox
categoriesYesList of category names along X-axis / slices
chart_typeYesChart type: COLUMN_CLUSTERED, LINE, PIE, or BAR_CLUSTERED
has_legendNoWhether to render chart legend
slide_indexYes0-based index of slide to place chart on
show_gridlinesNoWhether to show major gridlines on value axis
legend_positionNoLegend position: top, bottom, left, rightright
presentation_idNoIn-memory presentation ID
show_data_labelsNoWhether to display numeric data labels on chart points/bars

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already disclose the write profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false). The description adds that the chart is 'native, editable' rather than a rendered image, which is genuine value. However, with auto_save/file_path defaults in play, it says nothing about persistence behavior, what happens on an out-of-range slide_index, or whether repeated calls stack charts on the same coordinates.

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?

Two sentences, front-loaded with the core action, followed by a compact capability list. Nothing is padded, though the support list is largely redundant with the enum and schema and could have been spent on usage or prerequisites instead.

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 schema coverage is 100%, so return values and field meanings are handled elsewhere. Still, for a 16-parameter write tool that places objects on a slide, the description omits the presentation-context requirement and placement/overwrite behavior an agent needs before calling.

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 is already documented, including chart_type enum, legend_position, and placement coordinates. The description's feature list (legend positioning, gridline toggling, data labels) merely echoes schema fields and adds no new meaning or constraints. Baseline 3 applies when the schema carries the load.

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 native, editable PowerPoint chart.' The word 'native, editable' implicitly separates it from add_image (a picture) and add_data_table (a table), and the second sentence enumerates supported chart types. It stops short of naming a sibling or explicitly contrasting with add_image/add_data_table, so it is clear but not sharply differentiated.

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?

No when-to-use guidance at all: nothing says to pick this over add_image when a visual is needed, or over add_data_table when tabular data suffices. Prerequisites are also absent – it never states that a presentation must be loaded (presentation_id or file_path) or that slide_index must reference an existing slide.

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