Skip to main content
Glama

drive_append_rows

Add rows after the last row of a Google Sheet in the registered Google Drive folders. Values are entered as if typed (numbers, dates and formulas are recognised). For a Google Doc use drive.append.

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>",
      "rows": "<rows>"
    },
    "name": "drive_append_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesDrive id or pasted link of a Google Sheet.
rowsYesRows to add: a list of rows, each a list of cell values.
sheetNoName of the sheet (tab). Default: the first one.
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

A3.8/5.0
Behavior3/5

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

Beyond the annotations, the description usefully discloses value coercion — numbers, dates and formulas are interpreted as if typed, which matters for formula-injection risk. It says nothing about whether a missing tab is created, how partial failures are handled, or what is returned to the caller; with readOnly=false, idempotent=false already declared, the added context is real but thin.

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?

Three short sentences, front-loaded with the operation and scope, followed by the value-interpretation caveat and the sibling redirect. Nothing is redundant.

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?

For a four-parameter append with no output schema and full annotation coverage, the description supplies the essentials: target resource, insertion point, value semantics and where to go for Docs. The only real gap is error/edge behavior when the specified sheet is absent.

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 coverage is 100%, so file, rows, sheet and in_workspace are all documented in the schema itself. The description's only added meaning is that rows land after the existing last row, which the schema does not express; the remaining parameters get no elaboration.

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?

The description gives a concrete verb and resource — adding rows to a Google Sheet — and pins the insertion point to 'after the last row', which separates it from in-place edits like drive_update_range. It does not explicitly name the sheet-update sibling, so the differentiation from alternatives rests on inference.

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?

It states the correct target (Google Sheets with values as if typed) and explicitly redirects Google Docs work to drive.append, which is real routing guidance. It omits prerequisites such as write permission on the file or what happens when the named tab does not exist.

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.