gg-mcp

by tannht

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

add_sheet

Add a new sheet to an existing spreadsheet. Provide the spreadsheet ID and sheet name to create a new tab.

Instructions

Add a new sheet/tab to an existing 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": {
      "spreadsheet_id": "<spreadsheet_id>",
      "sheet_name": "<sheet_name>"
    },
    "name": "add_sheet"
  }
}

Input Schema

Name	Required	Description	Default
`spreadsheet_id`	Yes
`sheet_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Jun 23, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided. Description only states action but does not disclose edge cases (e.g., duplicate sheet name), required permissions, or side effects.

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?

Single sentence with no wasted words. Front-loaded with action and resource.

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?

No output schema; description lacks return value, error behavior, and behavior on success/failure. Incomplete for an AI agent to use effectively.

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

Parameters2/5

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

Schema description coverage is 0%. Description does not elaborate on parameter formats, restrictions, or how they are used. Parameter names are self-explanatory but no added value.

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?

Description clearly states action (add), resource (new sheet/tab), and context (to existing spreadsheet). Distinguishes from siblings like create_spreadsheet.

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 on when to use, when not to use, or alternatives. Missing prerequisites like spreadsheet existence or sheet name uniqueness.

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