Skip to main content
Glama

drive_append

Add text at the end of a Google Doc in the registered Google Drive folders, as a new paragraph. For a spreadsheet use drive.append_rows. file is a Drive id or a pasted link.

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>",
      "text": "<text>"
    },
    "name": "drive_append"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesDrive id or pasted link of a Google Doc.
textYesThe text to add.
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.1/5.0
Behavior4/5

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

Beyond the annotations, it discloses that content is inserted as a new paragraph (each call produces a separate paragraph), which is meaningful for an append operation with idempotentHint=false. It also reveals the access boundary (only registered Drive folders), a fact not encoded in the annotations. It does not cover failure behavior for invalid ids or non-Doc file types.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two front-loaded sentences covering behavior, the sibling alternative, and the key input convention. The final clause duplicates the schema's own parameter text, so it is slightly redundant rather than wasteful.

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 simple three-parameter append tool with full annotation coverage and no output schema, the definition supplies the essential behavior, the alternative tool, and the access scope. Missing only edge-case handling, which is minor at this complexity.

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 all three parameters are already documented. The sentence about `file` being a Drive id or pasted link merely repeats the schema text, and `in_workspace` is not discussed, so no real meaning is added.

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 and resource ('Add text at the end of a Google Doc ... as a new paragraph'), including the exact placement semantics. It also names the sibling to use for spreadsheets, so an agent can distinguish drive_append from drive_append_rows without opening either 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?

Explicitly routes spreadsheet cases to the sibling tool and scopes the operation to 'the registered Google Drive folders'. It gives clear context but stops short of stating when-not-to-use conditions (e.g. overwriting content should use drive_replace).

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.