Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

sheets_analyze

Read-only

Analyze a spreadsheet range or table to get column types, counts, blanks, distinct values, numeric statistics, and optional group-by summaries for quick data profiling.

Instructions

Analyze a table in a range (first row = headers): per-column type, count, blanks, distinct values, and for numeric columns sum/mean/median/min/max/stdev; top values for text columns. Optional group-by summary.

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>",
      "range": "<range>"
    },
    "name": "sheets_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYese.g. 'Sales' or 'Sales!A1:H500'
groupByNoHeader name to group by
spreadsheetIdYes
aggregateColumnsNoNumeric headers to sum/average per group

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds genuinely useful behavior beyond that by stating the first row is treated as headers and listing precisely which statistics are computed versus skipped (numeric-only sum/mean/etc., text-only top values). It stops short of noting limits such as large-range performance or error behavior on non-tabular input.

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 that opens with the action and then spends its clauses on concrete output fields, so nothing reads as filler. Dense but scannable; splitting the output enumeration into a short second sentence would be marginally clearer but is not required.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so by enumerating the per-column metrics it emits. Combined with annotations covering the read-only profile and the header-row convention, an agent has enough to call this correctly for a 4-parameter analysis tool.

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 75%, and the description clarifies the range semantics ('first row = headers') and that groupBy triggers a summary mode. However, aggregateColumns is never mentioned in the description, leaving the per-group sum/average behavior to the schema alone, so the added meaning is partial rather than compensating for the coverage gap.

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?

Uses a specific verb ('Analyze') and resource ('a table in a range') and enumerates exactly what is produced: per-column type, count, blanks, distinct, numeric aggregates, top text values. It implicitly distinguishes itself from raw-read siblings like sheets_read, but never names an alternative or states the contrast explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied through the header-row assumption and the 'Optional group-by summary' note, which tells an agent roughly when groupBy matters. There is no explicit when-to-use/when-not guidance, no prerequisites, and no routing away from sheets_read or sheets_get_info for simpler needs.

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