Skip to main content
Glama
logisky

logisheets-mcp

by logisky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

chart_insert

Insert a chart linked to spreadsheet ranges so it updates automatically when source cells change. Define series, categories, chart type, and placement to visualize data directly in the sheet.

Instructions

Insert a chart that reads its values live from the given ranges — editing those cells later updates the chart. Look at the data first so the series are right: a column of labels belongs in categoriesRef, each column of numbers is one series, and its header is that series' name. References are A1 (B2:B10, or Sheet2!B2:B10 to read another sheet). The chart is placed below the data unless anchor says otherwise.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoChart title.
anchorNoTop-left cell of the chart, e.g. 'H2'. Defaults to two rows below the data.
seriesYesOne entry per data series. Each valueRef is an A1 range of the values to plot.
sheetIdxYesSheet the chart is placed on (zero-based).
chartTypeYescol = vertical bars, bar = horizontal. pie/doughnut plot one series. scatter/bubble take numeric X from categoriesRef. stock needs 4 series (open/high/low/close) or 3 (high/low/close). surface plots a grid, one series per row.
sizeInCellsNoChart size in cells. Defaults to 15 × 8.
categoriesRefNoA1 range of the category labels (the X axis), e.g. A2:A10. For scatter/bubble these are the numeric X values.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds key behavioral traits: the chart is live-linked to the ranges (editing cells updates the chart) and default placement below data. These are useful beyond the annotations, though it does not disclose behavior on invalid ranges or chart type constraints (which are in the schema).

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?

Three sentences with no fluff. The core purpose is front-loaded, then data preparation guidance, then reference syntax and placement. Every sentence earns its place.

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 complex tool with 7 parameters and nested objects, the description covers the most critical aspects: data mapping, references, and placement. It does not explain all chart type nuances (e.g., bubble sizeRef, combo seriesType), but those are documented in the schema. The essential guidance for correct invocation is present.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant semantics beyond the schema. It explains the relationship between data columns and series/categoriesRef, gives A1 reference syntax including cross-sheet, and clarifies the default anchor placement. This is practical guidance an agent needs beyond raw parameter descriptions.

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 description clearly states the verb (insert) and resource (a chart) and distinguishes its key feature: values read live from given ranges. It also explains the placement behavior. This is specific and distinguishes from siblings like chart_from_block, which would use a block rather than ranges.

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?

The description gives clear context for how to use the tool: look at data first, map label column to categoriesRef, number columns to series, and use A1 references. It does not explicitly mention alternative tools like chart_from_block, but the live-range behavior implies when this tool is appropriate. No exclusions are given, but the context is strong.

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

Deploy Server

Other Tools