Excel MCP Server

Create chart

create_chart

Add a chart to an Excel worksheet from a selected data range, choosing column, bar, line, area, pie, or scatter chart types.

Instructions

Add a chart that plots a block of data.

'column' draws vertical bars, 'bar' horizontal bars. For 'scatter', the first column holds the x values.

Input Schema

TableJSON Schema

Name	Required	Description
`path`	Yes	Path to an .xlsx, .xlsm, .xltx or .xltm file. Relative paths are resolved in the server's workbook directory when one is configured; otherwise use an absolute path.
`sheet`	Yes	Worksheet name, e.g. 'Sheet1'.
`options`	No	Titles, size and legend. Default: none.
`chart_type`	Yes	Kind of chart to draw.
`data_range`	Yes	Data with a header row, labels in the first column and one series per further column, e.g. 'A1:C13'.
`data_sheet`	No	Sheet holding the data. Default: `sheet`.
`anchor_cell`	Yes	Cell where the chart's top-left sits.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedv1.1.1Sep 29, 2026

addedInput schema / $defs

Added value: +{
+  "ChartOptions": {
+    "description": "Chart titles, size and legend.",
+    "properties": {
+      "height_cm": {
+        "default": 7.5,
+        "description": "Chart height in cm.",
+        "exclusiveMinimum": 0,
+        "maximum": 100,
+        "title": "Height Cm",
+        "type": "number"
+      },
+      "show_legend": {
+        "default": true,
+        "description": "Show the series legend.",
+        "title": "Show Legend",
+        "type": "boolean"
+      },
+      "title": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Chart title.",
+        "title": "Title"
+      },
+      "width_cm": {
+        "default": 15,
+        "description": "Chart width in cm.",
+        "exclusiveMinimum": 0,
+        "maximum": 100,
+        "title": "Width Cm",
+        "type": "number"
+      },
+      "x_axis_title": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Horizontal axis title.",
+        "title": "X Axis Title"
+      },
+      "y_axis_title": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Vertical axis title.",
+        "title": "Y Axis Title"
+      }
+    },
+    "title": "ChartOptions",
+    "type": "object"
+  }
+}

addedInput schema / properties / anchor_cell

Added value: +{
+  "description": "Cell where the chart's top-left sits.",
+  "title": "Anchor Cell",
+  "type": "string"
+}

addedInput schema / properties / chart_type / description
```
Added value: +"Kind of chart to draw."
```

addedInput schema / properties / chart_type / enum

Added value: +[
+  "column",
+  "bar",
+  "line",
+  "area",
+  "pie",
+  "scatter"
+]

addedInput schema / properties / data_range / description

Added value: +"Data with a header row, labels in the first column and one series per further column, e.g. 'A1:C13'."

addedInput schema / properties / data_sheet

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Sheet holding the data. Default: `sheet`.",
+  "title": "Data Sheet"
+}

removedInput schema / properties / filepath

Removed value: -{
-  "title": "Filepath",
-  "type": "string"
-}

addedInput schema / properties / options

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/ChartOptions"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Titles, size and legend. Default: none."
+}

addedInput schema / properties / path

Added value: +{
+  "description": "Path to an .xlsx, .xlsm, .xltx or .xltm file. Relative paths are resolved in the server's workbook directory when one is configured; otherwise use an absolute path.",
+  "title": "Path",
+  "type": "string"
+}

addedInput schema / properties / sheet

Added value: +{
+  "description": "Worksheet name, e.g. 'Sheet1'.",
+  "title": "Sheet",
+  "type": "string"
+}

removedInput schema / properties / sheet_name

Removed value: -{
-  "title": "Sheet Name",
-  "type": "string"
-}

removedInput schema / properties / target_cell

Removed value: -{
-  "title": "Target Cell",
-  "type": "string"
-}

removedInput schema / properties / title

Removed value: -{
-  "default": "",
-  "title": "Title",
-  "type": "string"
-}

removedInput schema / properties / x_axis

Removed value: -{
-  "default": "",
-  "title": "X Axis",
-  "type": "string"
-}

removedInput schema / properties / y_axis

Removed value: -{
-  "default": "",
-  "title": "Y Axis",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "filepath",
-  "sheet_name",
-  "data_range",
-  "chart_type",
-  "target_cell"
-]New value: +[
+  "path",
+  "sheet",
+  "data_range",
+  "chart_type",
+  "anchor_cell"
+]

First observedv1.0.0Aug 15, 2025

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is largely covered. The description adds chart-type rendering semantics but says nothing about whether an existing chart at the anchor is replaced, whether the target sheet must already exist, or any failure modes for a mutating tool.

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, front-loaded sentences with no filler; the core purpose comes first and the type clarifications follow. Minor line-break formatting is slightly awkward but nothing is wasted.

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?

With an output schema present, return values need no explanation, and 100% schema coverage handles the parameters. The definition is adequate for calling the tool, with only prerequisites (existing sheet, anchor behavior) left implicit.

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?

Schema description coverage is 100%, so the baseline is 3, but the description goes further by explaining that 'column' draws vertical bars, 'bar' horizontal bars, and that for 'scatter' the first column holds x values — meaningful detail about chart_type that the enum alone does not convey.

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 ('Add a chart that plots a block of data') and clarifies the sub-semantics of several chart types. An agent can identify the tool's function immediately, though it never positions itself against related siblings like create_table or create_summary_table.

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?

There is no when-to-use, when-not-to-use, prerequisite, or alternative guidance. The description explains what the chart-type values mean but never says when an agent should reach for create_chart instead of create_table or a plain write_range.

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