Skip to main content
Glama
Sign In
Google Workspace MCP Server

Google Workspace MCP Server

by sahildhurat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

append_to_google_doc

Append text content to the end of a specified Google Doc, with optional timestamp heading and leading newline.

Instructions

Append text content to the end of an existing Google Doc.

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": {
      "document_id": "<document_id>",
      "content": "<content>"
    },
    "name": "append_to_google_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes
document_idYes
leading_newlineNo
add_timestamp_headingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations provided. The description only indicates a write operation but omits details like authentication, error cases, and parameter effects (e.g., leading_newline, add_timestamp_heading). Insufficient for full transparency.

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

Conciseness3/5

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

The description is a single sentence, which is concise but fails to convey essential usage details.

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

Completeness1/5

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

For a tool with 4 parameters and no annotations, the description is severely incomplete, missing parameter semantics, return values, and behavioral notes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%. The description adds no explanation of parameters (content, document_id, leading_newline, add_timestamp_heading) beyond their names.

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?

The description clearly states the specific verb 'Append' and the resource 'Google Doc', and it distinguishes from sibling email tools.

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 description implies using this tool when needing to add text to a document. Siblings are unrelated (email tools), so no confusion, but no explicit when-not-to-use guidance.

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

Deploy Server

Other Tools