Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

sheets_add_chart

Add a column, bar, line, area, pie, or scatter chart to a spreadsheet tab using data from a chosen range and columns.

Instructions

Add a chart (column, bar, line, area, pie, scatter) built from a data range on a tab.

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": {
      "spreadsheetId": "<spreadsheetId>",
      "tab": "<tab>",
      "startRow": "<startRow>",
      "endRow": "<endRow>",
      "domainCol": "<domainCol>",
      "seriesCols": "<seriesCols>"
    },
    "name": "sheets_add_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabYes
titleNo
endRowYesexclusive
startRowYes0-based header row
chartTypeNoCOLUMN
domainColYes0-based column with labels/x values
seriesColsYes0-based columns with values
spreadsheetIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not say where the chart is placed, whether it can overwrite existing content, what permissions are needed, or what is returned on success.

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?

A single front-loaded sentence with no filler; the chart-type list is compact and useful. It is arguably too terse for an 8-parameter mutation tool, but nothing is wasted.

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 mutation tool with 8 parameters, 6 required, no output schema and only 50% schema coverage, the description is thin. It omits where the chart lands, how the range maps to domain/series columns, and what the caller gets back, all of which an agent needs to invoke it correctly.

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 coverage is 50%; the schema itself documents startRow, endRow, domainCol, seriesCols and the chartType enum with a default. The description only echoes the chart types and the notion of a tab, leaving title and spreadsheetId unexplained, so it adds marginal meaning over the schema.

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?

The description gives a specific verb ('Add') and resource ('chart'), enumerates the supported chart types, and states the data source ('a data range on a tab'). It is clearly distinguishable from siblings like sheets_format or sheets_write, though it never names an alternative explicitly.

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 guidance, no prerequisites (e.g. that the tab and range must already contain data), and no mention of alternatives such as sheets_format for non-chart styling. The only implied context is that a data range on a tab must exist.

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