Skip to main content
Glama
Alex-eng-ux

Office MCP Server

by Alex-eng-ux

Add Shape Slide to PowerPoint

office_ppt_add_shape
Destructive

Create a PowerPoint file with a single slide containing a specified shape. Supports customizable position, size, colors, rotation, and many shape types.

Instructions

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

Args:

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

  • shape (string): Shape type name (e.g. 'rect', 'ellipse', 'triangle', 'star5', 'heart', 'cloud', 'lightningBolt', 'smileyFace', 'chevron', 'pentagon', 'hexagon', 'octagon', 'diamond', 'moon', 'sun', 'pie', 'arc', 'frame', 'cube', 'plus', 'wave', 'funnel', 'bevel', 'donut', 'corner', 'heart', 'plaque', 'ribbon', 'line', etc.)

  • options (object, optional):

    • x (number): Left position (inches)

    • y (number): Top position (inches)

    • w (number): Width (inches)

    • h (number): Height (inches)

    • fillColor (string): Fill color (hex, e.g. "4472C4")

    • lineColor (string): Line/border color (hex)

    • lineSize (number): Line width (points)

    • rotate (number): Rotation (degrees, -360 to 360)

Examples:

  • Use when: "Draw a red rectangle" or "Create a slide with a blue circle"

  • Use when: "Add a star shape to the presentation"

  • Use when: "Create a flowchart shape like a diamond or process box"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesPath for the new PowerPoint file
shapeYesShape type (e.g. 'rect', 'ellipse', 'triangle', 'star5', 'heart', 'diamond', 'chevron', 'lightningBolt', 'cloud', 'smileyFace', 'moon', 'sun', 'pentagon', 'hexagon', 'octagon', 'pie', 'arc', 'cube', 'plus', 'wave', 'funnel', 'ribbon', 'line', 'bentArrow', 'circularArrow', 'leftArrow', 'rightArrow', 'upArrow', 'downArrow')
optionsNoShape options
Behavior3/5

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

The description aligns with annotations (destructiveHint: true, readOnlyHint: false) by stating it creates a new file. However, it does not disclose whether the tool overwrites existing files or how it behaves if the file already exists, which is important for a destructive operation.

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 well-structured with separate 'Args' and 'Examples' sections. It is concise and front-loaded with the core action. Minor redundancy in shape examples could be trimmed, but overall efficient.

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?

For a tool with nested options and 3 parameters, the description covers essential usage. However, it omits details about file overwrite behavior, return values, and the fact that only one shape per slide is supported. This leaves gaps for an agent to infer correctly.

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?

Input schema has 100% coverage with parameter descriptions. The description adds value by listing additional shape examples beyond the schema, but it largely duplicates the schema information. Baseline 3 is appropriate as schema does the heavy lifting.

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 clearly states it creates a new PPTX with one slide containing a shape. However, the title 'Add Shape Slide to PowerPoint' is misleading as it implies adding to an existing presentation, not creating a new file. This discrepancy reduces clarity.

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 description includes 'Use when:' examples that provide usage context, but it fails to explicitly state when NOT to use this tool (e.g., for adding shapes to existing presentations). Siblings like office_ppt_add_chart exist, but no differentiation is given.

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