Skip to main content
Glama

format_shapes

Apply fill color and font formatting to multiple shapes on a PowerPoint slide in one call, preserving the current view position while updating shapes in place.

Instructions

Apply formatting to multiple shapes on a slide in one call. Generates Office.js code internally. Use for fill color, font bold/italic/size/color/name. Cannot set corner radius or borders (use edit_slide_xml code mode for those). Runs in place (no slide reimport), so PowerPoint view position is preserved.

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": "<slide>",
      "shapes": "<shapes>"
    },
    "name": "format_shapes"
  }
}

Input Schema

NameRequiredDescriptionDefault
slideYesSlide number, 1-based (slide 1 = first slide)
shapesYesShapes to format with their properties
presentationIdNoTarget presentation ID from list_presentations. Optional when only one presentation is connected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.7.1
    • addedInput schema / properties / slide
      Added value: +{
      +  "description": "Slide number, 1-based (slide 1 = first slide)",
      +  "maximum": 9007199254740991,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • removedInput schema / properties / slideIndex
      Removed value: -{
      -  "description": "Zero-based slide index",
      -  "maximum": 9007199254740991,
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "slideIndex",
      -  "shapes"
      -]New value: +[
      +  "slide",
      +  "shapes"
      +]
  2. First observedv0.6.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it explains that Office.js code is generated internally and that the edit runs in place without slide reimport, preserving PowerPoint view position. It does not cover failure behavior for invalid shape IDs or whether changes are undoable, so it stops short of full transparency.

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?

Four short sentences, none wasted, with the capability statement front-loaded and the limitation/alternative placed immediately after. The in-place execution note is the only trailing item and it earns its place by explaining a side effect the agent would otherwise not expect.

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?

For a mutation tool with no annotations and no output schema, the description covers purpose, supported and unsupported operations, the alternative tool, and the execution model. It could still say whether shape IDs must belong to the given slide or what happens on partial failure, which is the main residual gap.

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 slide, presentationId, and each shape property are already documented in the schema. The description mentions the format categories but adds no syntax, defaults, or partial-update semantics beyond what the schema states, so baseline 3 applies.

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?

States a specific verb and resource (apply formatting to shapes), plus scope qualifiers: multiple shapes, one slide, single call. It also enumerates the supported properties and names the sibling tool needed for the unsupported ones, so it is distinguishable from format_paragraph and edit_slide_xml at a glance.

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?

Explicitly says what it is for (fill color, font bold/italic/size/color/name) and what it cannot do (corner radius, borders), routing the agent to edit_slide_xml code mode for the exclusions. That is a when-to-use plus an alternative, not just implied usage.

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