Skip to main content
Glama
Hermoso

Hermoso

Official

Create a Google Doc

create_doc

Create a Google Doc in Drive with a title and optional body text, then return its document ID and URL. Use it to export ad copy, briefs, or reports.

Instructions

Create a new Google Doc in the user’s Drive with a title + optional body text — e.g. export ad copy, a creative brief, or a report. Returns the document id + URL. Needs Google Drive connected (Connectors > Google Drive — one connection covers Drive, Sheets and Docs).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNobody text to insert
titleNodocument title

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.161

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true). The description goes beyond them by disclosing the return payload ('document id + URL') and the auth/connect prerequisite, both of which an agent needs before calling. It does not mention what happens if title is omitted or whether duplicate titles create duplicate docs, which idempotentHint=false hints at but doesn't explain.

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?

Purpose and use cases are front-loaded in the first sentence, which is good structure. The trailing parenthetical about Connectors covers necessary setup but is dense and slightly buried at the end rather than framed as a precondition up front.

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 two-parameter create tool with no output schema, the description covers purpose, payload, return value, and prerequisite. The remaining gaps are edge cases (behavior with missing title, duplicate documents), which are minor but would matter for a non-idempotent write.

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 both properties are already documented in the schema, making 3 the baseline. The description restates the same field meanings without adding format guidance, defaults, or behavior when fields are absent — and its 'title + optional body text' phrasing mildly implies title is required when the schema marks nothing required.

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?

States a specific verb and resource ('Create a new Google Doc in the user's Drive') and enumerates the payload ('title + optional body text'). The word 'new' implicitly separates it from append_to_doc/update_doc siblings, but it never names them, so differentiation is inferred rather than stated.

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?

Gives concrete use contexts ('export ad copy, a creative brief, or a report') and a prerequisite (Drive must be connected). It does not state when to prefer a sibling such as append_to_doc or create_sheet instead, so it stops short of full routing 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