mcp-google-sheets-server

sheets_set_formula

Set formulas in a specified range of a Google Sheet by providing the spreadsheet ID, target range, and an array of formulas.

Instructions

Set formulas in cells

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>",
      "formulas": "<formulas>"
    },
    "name": "sheets_set_formula"
  }
}

Input Schema

Name	Required	Description
`range`	Yes	The range to set formulas
`formulas`	Yes	Array of formulas to set
`spreadsheetId`	Yes	The ID of the spreadsheet

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.1Sep 7, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries full responsibility for revealing behavior. It states 'set formulas' but does not disclose side effects like overwriting existing formulas, expected formula format (e.g., leading '='), or that it is a write operation.

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?

One short, direct sentence with no redundant wording. Perfectly concise for the intended purpose.

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

Completeness3/5

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

Sufficient for a simple setter, but lacks context on error handling, confirmation of written data, or interaction with existing cell content. No output schema is provided, which is acceptable for a write operation.

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 descriptions cover the basics (range, formulas, spreadsheet ID) but lack detail on formula syntax, array dimensions matching the range, or whether the formulas parameter should be a flat list or 2D array.

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?

Clearly states the action (set) and resource (formulas in cells), distinguishing it from value-setting tools. However, it could be more specific about overwriting behavior or the need for A1 notation.

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 this tool versus siblings like sheets_update_data or sheets_batch_update. The description does not mention alternatives or prerequisites.

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