mcp-google-sheets-server

sheets_calculate_formula

Calculates a formula in a specified Google Sheets spreadsheet using the provided formula string and spreadsheet ID.

Instructions

Calculate the result of a formula

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>",
      "formula": "<formula>"
    },
    "name": "sheets_calculate_formula"
  }
}

Input Schema

Name	Required	Description	Default
`formula`	Yes	The formula to calculate
`spreadsheetId`	Yes	The ID of the spreadsheet

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.1Sep 7, 2026

TDQS

C2.4/5.0

Behavior2/5

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

The description implies a read-only calculation but does not explicitly state that no spreadsheet data is modified, nor does it mention return format or error behavior. With no annotations, the agent is left without important behavioral expectations.

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 a single concise sentence with no extraneous words. It is appropriately short for the limited information provided.

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?

With no output schema and minimal description, critical context is missing: the agent does not know what the function returns, whether it returns a scalar value, or how formula references are resolved. This makes the tool difficult to use reliably.

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?

The schema lists spreadsheetId and formula, but the descriptions merely repeat the parameter names without adding meaning. There is no explanation of formula syntax, whether a leading '=' is expected, or what spreadsheet context is used for calculation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the verb 'Calculate' and the resource 'formula', so the basic purpose is identifiable. However, it does not clarify whether this evaluates a formula string in the spreadsheet context or returns a computed value, and it does not distinguish it from sheets_set_formula.

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

Usage Guidelines1/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 like sheets_set_formula or sheets_get_data. The description gives no context for when formula evaluation is appropriate, leaving the agent to guess.

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