Skip to main content
Glama
lmdat

@lmdat/google-sheets-oauth-mcp

by lmdat

Tạo chart cơ bản trong Google Sheet

sheets_create_chart

Create a chart (column, bar, line, area, scatter, or pie) directly in a Google Sheet tab from existing data. Specify sheet-qualified ranges for domain and series.

Instructions

Tạo 1 chart COLUMN/BAR/LINE/AREA/SCATTER/PIE từ data có sẵn, chart được embed thẳng vào tab. Mọi range PHẢI ghi đủ tên sheet, dạng "TenSheet!A2:A10" — không hỗ trợ range thiếu tên sheet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTiêu đề chart.
stackedNoChỉ có ý nghĩa với COLUMN/BAR/AREA. true = stacked chart.
chart_typeYes
anchor_cellNoVị trí góc trên-trái đặt chart, dạng "TenSheet!F2". Bỏ trống -> tự đặt ngay bên phải domain_range.
domain_rangeYesRange nhãn trục X (category/labels), dạng "TenSheet!A2:A10". Với PIE đây là nhãn từng phần.
series_rangesYesRange giá trị, mỗi string là 1 series, dạng "TenSheet!B2:B10". PIE chỉ nhận đúng 1 series.
spreadsheet_idYesID của Google Sheet — lấy từ URL (docs.google.com/spreadsheets/d/<ID>/edit) hoặc dùng tool drive_list_spreadsheets để tìm theo tên.
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that charts are embedded directly into tabs, that stacked only applies to certain types, and that PIE accepts exactly one series. However, it does not mention potential destructive behavior, permissions, or output details.

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?

The description is two sentences with no fluff. It front-loads the main purpose and immediately provides critical usage guidance on range format.

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 creation tool with 7 parameters and no output schema, the description covers the key behavioral aspects and parameter constraints. It could mention return values (e.g., chart ID) or error handling, but it is sufficient for an AI agent to use correctly.

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

Parameters4/5

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

Schema description coverage is high (86%), so baseline is 3. The description adds value by specifying that ranges must include sheet names and clarifying type-specific constraints (stacked only for COLUMN/BAR/AREA, PIE one series). This goes beyond the schema.

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 it creates basic charts (COLUMN/BAR/LINE/AREA/SCATTER/PIE) from existing data and embeds them into a sheet. It distinguishes from the sibling 'sheets_create_candlestick_chart' by listing supported chart types.

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 explicitly requires ranges to include sheet names, providing a concrete usage guideline. It does not explicitly mention when to avoid using this tool, but the sibling list implies alternatives exist for candlestick charts.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lmdat/google-sheet-oauth-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server