Skip to main content
Glama
Alex-eng-ux

Office MCP Server

by Alex-eng-ux

Add Chart Slide to PowerPoint

office_ppt_add_chart
Destructive

Generate a PowerPoint slide with a chart from data series. Choose from area, bar, bubble, doughnut, line, pie, radar, or scatter charts with optional legends, titles, and colors.

Instructions

Create a new PowerPoint (.pptx) with one slide containing a chart.

Args:

  • filePath (string): Path where the presentation will be created

  • chart (object): Chart configuration

    • type (string): Chart type: "area" | "bar" | "bar3D" | "bubble" | "doughnut" | "line" | "pie" | "radar" | "scatter"

    • data (array): Data series. Each series has:

      • labels (string[]): Category labels

      • name (string): Series name

      • values (number[]): Data values

    • options (object, optional):

      • showLegend (boolean): Show legend

      • showTitle (boolean): Show title

      • chartColors (string[]): Custom color palette

      • barDirection ("bar" | "col"): Bar direction (for bar charts)

      • barGrouping ("clustered" | "stacked" | "percentStacked"): Bar grouping

      • dataLabelFormat (string): Data label format code (e.g. "#,##0")

Examples:

  • Use when: "Create a bar chart showing quarterly sales data"

  • Use when: "Generate a pie chart of market share distribution"

  • Use when: "Make a line chart of revenue trends over time"

  • Not for: Simple text slides with bullets (use office_create_powerpoint instead)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesPath for the new PowerPoint file
chartYes
Behavior4/5

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

Annotations indicate destructiveHint: true, which aligns with the description's 'Create a new PowerPoint...'. The description adds that it creates a new file, but does not explicitly mention overwrite behavior. No contradiction with annotations.

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 description is effectively structured with Args section and examples, front-loading the main purpose. It is comprehensive but slightly lengthy; each section contributes value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (nested chart config), the description covers purpose, parameters, and usage guidance. However, it lacks explanation of return values (no output schema) and could clarify file overwrite behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description re-explains parameters like chart type, data series structure, and options in a structured format, adding value beyond the schema. However, it could more clearly differentiate required vs optional for nested fields; schema coverage is moderate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a new PowerPoint file with a chart slide, using specific verbs 'Create' and 'containing a chart'. It distinguishes from siblings like office_create_powerpoint (which likely creates a blank presentation) and other office_ppt_add_* tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit 'Use when' and 'Not for' examples, guiding the agent on appropriate use cases (e.g., chart generation) and exclusion of simple text slides with reference to an alternative sibling tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Alex-eng-ux/office-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server