Skip to main content
Glama

drive_create_doc

Create a new Google Doc (or Sheet, with kind='sheet') inside a folder of a Shared Drive that is registered for this workspace, optionally with starting text. In a folder of someone's My Drive the file is made through the workspace's Google Workspace integration (it needs one connected) and moved into the folder.

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": {
      "name": "<name>",
      "folder": "<folder>"
    },
    "name": "drive_create_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNodoc (default) or sheet.doc
nameYesName of the new file.
textNoStarting text (documents only).
folderYesDrive id or pasted link of the folder to create it in.
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.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (not read-only, not destructive, not idempotent, closed-world), so the bar is lower. The description adds genuine context beyond them: the two-step behavior for My Drive folders, the dependency on a connected Google Workspace integration, and the fact that the file is then moved into the folder. It does not address what happens on a name collision, which matters given idempotentHint=false, nor what identifiers come back.

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 sentences, front-loaded with the primary action and the sheet variant before the fallback path. The second sentence is dense and slightly convoluted, but each clause carries information an agent would otherwise have to discover.

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 non-idempotent create tool with no output schema, the description covers the main operational risk (folder location determines which integration path runs and whether a connection is required). The main remaining gap is the return value and collision behavior, which is tolerable but not ideal given no output schema exists.

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 five parameters are already documented, including the kind enum, name length cap, text being documents-only, and folder accepting a Drive id or pasted link. The description reinforces only kind and text, which the schema already states, and never mentions the in_workspace parameter. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

A specific verb plus resource: create a new Google Doc or Sheet in a folder. It also names the routing nuance (Shared Drive folder vs. My Drive folder), which is more than the name conveys. It stops short of distinguishing itself from plausible siblings like drive_upload, drive_import, or documents_create, so an agent still has to infer which creation path applies.

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 gives usable conditional guidance: if the folder sits in a Shared Drive registered for this workspace, use this tool directly; if it is in someone's My Drive, the file is created via the workspace's Google Workspace integration, which must be connected. That is a real prerequisite an agent needs before calling. It does not explicitly exclude or point to alternative tools for other creation scenarios.

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.