Excel MCP Server

Add sparklines

add_sparklines

Insert sparklines into Excel cells from a source range, placing one per row or column and replacing existing sparklines in the target range.

Instructions

Add sparklines (Insert > Sparklines) to the cells of range, one per row of source (per column when the cells match the columns). Replaces existing ones there.

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": {
      "path": "<path>",
      "sheet": "<sheet>",
      "range": "<range>",
      "source": "<source>"
    },
    "name": "add_sparklines"
  }
}

Input Schema

Name	Required	Description
`path`	Yes
`range`	Yes	One row or column, e.g. 'G2:G9'.
`sheet`	Yes
`style`	No
`source`	Yes	Data, e.g. 'Data!B2:F9': a sparkline per row.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.0.0Oct 13, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnly=false, destructive=false, openWorld=false) but say nothing about content replacement. The description explicitly discloses that existing sparklines in `range` are overwritten, which is a genuinely useful behavioral fact an agent would otherwise miss. It adds no other context such as permission needs or error behavior.

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 tightly written sentences with the core action and placement rule front-loaded; every clause carries information (placement direction, column-match case, overwrite behavior). No filler.

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 mutation tool with no output schema and 40% schema coverage, the description explains the key structural contract but leaves the rich `style` parameter and any failure/permission behavior undocumented. An agent can call it, but only with the schema as a crutch.

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?

With schema coverage at only 40%, the description carries extra weight and does clarify the crucial `range` vs `source` relationship (per-row, or per-column on column match). However `style` — a large nested object with many sub-options — is never mentioned in the description, and `path`/`sheet` are assumed. Partial compensation only.

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+resource (add sparklines) and nails down the placement semantics: one sparkline per row of `source`, or per column when the cells match the columns. The parenthetical '(Insert > Sparklines)' anchors it to the UI equivalent. It does not explicitly name the sibling `delete_sparklines`, so it falls just short of a 5.

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?

The description says what happens (replaces existing sparklines there) but never states when to reach for this tool versus alternatives such as deleting first with `delete_sparklines`, nor any prerequisites like needing an existing sheet. Usage must be inferred entirely from the mechanics.

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