Skip to main content
Glama

edit_slide_chart

Create a chart on a slide from structured data by specifying chart type, title, categories, and series; OOXML is generated automatically.

Instructions

Create a chart on a slide from structured data. Generates all OOXML automatically (chart XML, rels, graphic frame, Content_Types). Supports column, bar, line, pie, doughnut, and area charts with multiple series.

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>",
      "chartType": "<chartType>",
      "title": "<title>",
      "categories": "<categories>",
      "series": "<series>"
    },
    "name": "edit_slide_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
slideYesSlide number, 1-based (slide 1 = first slide)
titleYesChart title
seriesYesData series
optionsNoChart options
positionNoChart position in points. Defaults to centered on slide.
chartTypeYesChart type
categoriesYesCategory labels (x-axis or pie slices)
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",
      -  "chartType",
      -  "title",
      -  "categories",
      -  "series"
      -]New value: +[
      +  "slide",
      +  "chartType",
      +  "title",
      +  "categories",
      +  "series"
      +]
  2. First observedv0.6.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does usefully disclose that all OOXML (chart XML, rels, graphic frame, Content_Types) is generated automatically, which tells the agent it need not hand-author XML, but it says nothing about whether an existing chart on the slide is replaced, what permissions or connected-presentation state are required, or what the call returns.

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?

Three short sentences, front-loaded with the core action, with no filler. The OOXML parenthetical is slightly implementation-flavored but earns its place by telling the agent no manual XML assembly is needed.

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 an 8-parameter mutation tool with nested objects and no output schema, the description covers what the tool builds but omits return/side-effect behavior and the overwrite semantics. Since the schema fully documents inputs, the remaining gap is mostly about post-call expectations.

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%, including nested series, options, position, and the chartType enum, so the schema does the heavy lifting. The description only reinforces the chart-type set and the multi-series capability, adding little meaning beyond that baseline.

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 chart on a slide from structured data', and enumerates the supported chart types. It does not, however, distinguish itself from the sibling 'add_chart' (which appears to target workbooks), so an agent must infer that this tool is the slide/presentation variant rather than the spreadsheet one.

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?

Use is implied by the 'on a slide' scoping and the schema's presentationId/slide parameters, but there is no explicit when-to-use guidance, no prerequisites (e.g., slide must already exist), and no naming of alternatives such as add_chart or edit_slide_xml for cases the structured API does not cover.

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