Skip to main content
Glama
Longtran2404

mcp-google-sheets-server

by Longtran2404

sheets_create_chart_with_data

Create a chart in Google Sheets from a specified data range, with options for chart type, title, and placement.

Instructions

Create a chart with data and automatically populate it

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoTitle of the chart
positionNoPosition where to place the chart
chartTypeYesType of chart to create
dataRangeYesRange containing the data for the chart (e.g., A1:C10)
chartOptionsNoAdditional chart options like colors, legends, etc.
spreadsheetIdYesThe ID of the spreadsheet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of explaining side effects, but it only says the chart is created and populated. It does not disclose whether an existing chart is overwritten, whether write access is required, or what output/response format to expect.

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?

The description is a single, concise sentence with no unnecessary fluff. It is appropriately sized for the tool's purpose, though slightly vague in wording.

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?

The tool has multiple parameters including nested objects and no output schema, but the description and parameter summaries do not explain how to construct position or chartOptions, nor what the tool returns. More context is needed for an agent to call 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?

All six parameters have short descriptions, covering 100% of the schema, but nested objects like position and chartOptions are only vaguely described. The descriptions add basic meaning but do not provide enough detail about nested structures or expected values.

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 identifies a specific action (create) and object (chart with data), and clarifies that it automatically populates the chart from the provided data range. However, it does not explicitly distinguish itself from sibling tools like sheets_create_chart or sheets_create_chart_from_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?

No guidance is provided about when to use this tool versus alternatives such as sheets_create_chart_from_table or sheets_update_chart_data. There are no usage conditions, prerequisites, or exclusions mentioned.

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