Skip to main content
Glama

drive_update_range

Overwrite a range of a Google Sheet in the registered Google Drive folders, such as 'Sheet1'!B2:C3. Values are entered as if typed. To add rows at the end use drive.append_rows.

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": {
      "file": "<file>",
      "range": "<range>",
      "values": "<values>"
    },
    "name": "drive_update_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesDrive id or pasted link of a Google Sheet.
rangeYesA1 range, e.g. 'Sheet1'!B2:C3.
valuesYesThe new values: a list of rows, each a list of cell values.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, it discloses that 'Values are entered as if typed' — a meaningful behavioral trait about type coercion and formula interpretation that is not in any structured field. It also scopes operations to 'the registered Google Drive folders,' which clarifies reachability. Minor tension: 'Overwrite' implies replacing existing cell contents while destructiveHint=false, though since the range is explicit this reads as scoped mutation rather than a contradiction; it does not say what happens when the range exceeds existing sheet bounds.

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?

Two sentences, front-loaded with the operation and target, followed immediately by the sibling routing. Every clause carries load; nothing is restated or padded.

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

Completeness4/5

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

With a fully documented schema and no output schema, the description covers what the tool does, the key write semantics, and the primary alternative. What is missing is modest: return/result information (e.g., updated range or cell count) and error behavior for out-of-bounds ranges.

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 description coverage is 100%, so file, range, values, and in_workspace are already documented in the schema; the description adds no additional meaning for any parameter. The A1 range example in the description duplicates the schema's own example, and in_workspace (the non-obvious 'run in another workspace' parameter) is not addressed at all.

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?

States a specific verb ('Overwrite') and resource ('a range of a Google Sheet'), plus a concrete example range ('Sheet1'!B2:C3). It also names the sibling it is not (drive.append_rows), so an agent can distinguish it from the append tools without opening a schema.

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

Usage Guidelines4/5

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

The final sentence gives explicit routing: 'To add rows at the end use drive.append_rows,' which is exactly the common ambiguity for a sheet-write tool. It stops short of stating when not to use it (e.g., ranges that fall outside the sheet's current dimensions, or partial edits better served by drive_replace), so it is clear context without full exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.