gg-mcp

by tannht

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

create_spreadsheet

Create a new Google Sheets spreadsheet by specifying a title and optionally the first sheet name.

Instructions

Create a new Google Sheets spreadsheet.

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": {
      "title": "<title>"
    },
    "name": "create_spreadsheet"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes
`sheet_name`	No		Sheet1

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Jun 23, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description must fully convey behavioral traits. It only states 'Create a new Google Sheets spreadsheet' without disclosing side effects (e.g., where the spreadsheet is stored, permissions required, rate limits, or return behavior). This minimal information provides insufficient transparency for an agent to assess operational impact.

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 that directly states the tool's primary function. It avoids unnecessary words and is front-loaded with the key action and resource. While it could be expanded slightly, it remains efficient given the tool's simplicity.

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?

Given the tool has 2 parameters (one required) and no output schema or annotations, the description should at least explain parameter behavior and return value. It only says 'Create a new Google Sheets spreadsheet', omitting what the spreadsheet is named with, default sheet name behavior, and any output confirmation. This lack of completeness leaves significant gaps for correct invocation.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must compensate by explaining the parameters. However, the description does not mention the 'title' or 'sheet_name' parameters at all, providing no additional meaning beyond the schema field names. The agent lacks guidance on how to set these values correctly.

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 'Create' and the resource 'a new Google Sheets spreadsheet', which directly distinguishes it from sibling tools like 'update_spreadsheet', 'read_spreadsheet', and 'append_to_spreadsheet'. The resource type is specific to Google Sheets, avoiding ambiguity.

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 on when to use this tool versus alternatives such as 'create_document', 'update_spreadsheet', or 'batch_update_spreadsheet'. The description does not mention prerequisites, context, or exclusion criteria, leaving the agent to infer usage from the name alone.

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