SheetForge MCP

Overview Schema Source Related Servers Discussions Admin

create_chart

Destructive

Create charts in Excel worksheets from a contiguous data range or explicit series, with options for chart type, title, axes, placement, and styling.

Instructions

Create chart in worksheet from a contiguous range or explicit series.

This is the preferred chart authoring entry point; explicit-series calls are
also still available via create_chart_from_series for backward compatibility.

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": {
      "filepath": "<filepath>",
      "sheet_name": "<sheet_name>",
      "chart_type": "<chart_type>"
    },
    "name": "create_chart"
  }
}

Input Schema

Name	Required	Description
`style`	No
`title`	No
`width`	No
`height`	No
`series`	No
`x_axis`	No
`y_axis`	No
`filepath`	Yes	Reuse supplied server path; NEVER prepend client cwd. Rooted: relative OK; unrooted stdio: absolute, ask if missing.
`placement`	No
`chart_type`	Yes
`data_range`	No
`sheet_name`	Yes
`target_cell`	No
`categories_range`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.14.0Oct 31, 2026

addedInput schema / properties / filepath / description

Added value: +"Reuse supplied server path; NEVER prepend client cwd. Rooted: relative OK; unrooted stdio: absolute, ask if missing."

First observedv0.8.0Aug 7, 2026

TDQS

A3.5/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true, but the description adds no behavioral context about what may be overwritten (e.g., an existing chart at target_cell), placement side effects, or permissions. It is consistent with the create mutation, so no contradiction, but it does not go beyond the annotation.

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?

Two short sentences with the primary purpose front-loaded; the sibling note is useful routing rather than padding. There is essentially no wasted text.

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

Completeness2/5

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

For a 14-parameter mutation tool with 7% schema coverage and no output schema, the description is too thin. It does not cover required chart_type values, valid series/range forms, placement collision behavior, or output/return expectations.

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

Parameters2/5

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

Schema description coverage is only 7%; only filepath is documented. The description hints at data_range and series but says nothing about chart_type values, series object shape, placement, target_cell, categories_range, style, width/height, or axes, leaving most of 14 parameters unexplained.

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 first sentence gives a specific verb and resource ('Create chart in worksheet') and explicitly names the two input modes, contiguous range or explicit series. It also distinguishes this tool from sibling create_chart_from_series by calling itself the preferred entry point.

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

Usage Guidelines4/5

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

It states this is the preferred chart authoring entry point and directs legacy explicit-series use to create_chart_from_series. It does not explain when the sibling is actually required rather than merely available, nor when to prefer data_range over series, but the primary routing is explicit.

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

Deploy Server