Skip to main content
Glama

write_drive_file

Idempotent

Writes Markdown, Google Docs, Sheets, and Slide decks to the workspace, using MIME disambiguation to select the correct file format.

Instructions

Write a Markdown, Google Doc (.gdoc), Sheet (.gsheet), or Slide deck (.slides) to the workspace with INV-14 MIME disambiguation.

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": {
      "path": "<path>",
      "content": "<content>"
    },
    "name": "write_drive_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
contentYes
mime_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description usefully enumerates the supported document types, but it does not explain overwrite behavior for an existing path, whether parent directories are created, or what 'INV-14' means — leaving the most consequential write semantics implicit.

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 single sentence is front-loaded with the important information and is not padded. However, the cryptic 'INV-14' token consumes space without conveying meaning to the agent, so part of the sentence does not earn its place.

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?

For a mutation tool with three undocumented parameters and no output schema, the description should cover overwrite semantics, path resolution, and how mime_type interacts with the file extension. None of these are addressed, so an agent could invoke it correctly in form but not predict its side effects.

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?

Schema description coverage is 0%, so the description carries the full burden for path, content, and mime_type. It hints that MIME is disambiguated from the target type but never explains whether mime_type is optional, whether it is inferred from the extension, or what the path is relative to.

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 names a specific verb (write) and an explicit resource set (Markdown, .gdoc, .gsheet, .slides) targeting the workspace, which clearly distinguishes it from the read-only sibling read_drive_file. The trailing reference to 'INV-14 MIME disambiguation' is internal jargon that adds no clarity, but the core action is unambiguous.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus alternatives — it never contrasts with read_drive_file or says whether it creates or overwrites. The agent must infer usage entirely from the verb and the annotations.

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