Skip to main content
Glama

Coline

Write a doc

create_doc

Creates a paged document (a proposal, brief, report, letter). Write plain text or markdown-like text.

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": {
      "workspace": "<workspace>"
    },
    "name": "create_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
contentNo
driveIdNoDrive to put it in; default: the person's default writable drive.
parentIdNoFolder to put it in, in that drive.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
urlYes
textYes
docIdYes
titleYes
revisionYes
textTruncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world behavior, so the safety bar is low. The description adds genuine behavior context by telling the agent that content is stored as plain/markdown-like text rather than rich formatting, but says nothing about creation side effects (notifications, default drive selection) or size limits.

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 short sentences with the core action front-loaded and the document examples immediately after the verb. The second sentence is terse but relevant; nothing is padded, though the whole definition is arguably under-written rather than concise.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, but for a 5-parameter creation tool the description leaves placement (workspace/drive/folder) and post-creation behavior entirely to the schema. It is minimally adequate but does not fully cover the call's semantics.

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 coverage is 60% and the description never references workspace, driveId, parentId, or title, so the two undocumented parameters gain no meaning from the prose. The one thing it does clarify — that 'content' takes plain text or markdown-like text — is marginal next to the placement parameters that determine where the doc lands.

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 ('Creates a paged document') and concretizes the resource with examples (proposal, brief, report, letter), which separates it from sibling creators like create_note or create_sheet. It stops short of naming the near neighbors save_doc/update_doc, so the boundary is implied rather than drawn.

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 when-to-use or when-not-to-use guidance: nothing says whether this is used instead of save_doc or write_project_update, and no prerequisites (workspace membership, write access, limits) are mentioned. The only usage-adjacent content is the content-format hint, which is more of a parameter note than a selection rule.

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.

Resources