Skip to main content
Glama

word_create_document

Create a new .docx file at a specified path, with an optional title paragraph.

Instructions

Create a new .docx file at path with an optional title paragraph.

Args: path: Target .docx path. May be absolute or relative to folder (or to the default folder when folder is None). title: Optional text for the first paragraph. When None the document is created with a single empty paragraph (the python-docx default). folder: Optional base folder for relative paths.

Returns: {"path": "<absolute path>"} on success.

Raises: OfficeMCPError: ERR_INVALID_PARAMS if path is empty or a file already exists at the target. ERR_UNSUPPORTED_FMT if path does not end in .docx.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
titleNo
folderNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Discloses error conditions (file exists, invalid path format) and return value, but no annotations are provided to compensate. Behavior like no overwrite is implied but not explicitly stated. Could benefit from more detail on side effects and prerequisites.

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?

Front-loaded with a clear summary, then structured Args, Returns, Raises sections. Informative but slightly verbose; could be more concise without losing clarity.

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?

Covers essential aspects: purpose, parameters, return structure, and error cases. Missing some details like limitations or encoding, but adequate for a creation tool.

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

Parameters5/5

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

Despite 0% schema description coverage, the description explains each parameter thoroughly: path (relative/absolute), title (optional, default None), folder (base for relative). Adds meaning beyond the schema.

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?

Clearly states it creates a .docx file at a given path with an optional title paragraph. The verb 'create' and resource 'document' are specific, and it distinguishes from sibling tools that manipulate existing documents.

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?

Describes the tool's purpose but does not explicitly mention when to avoid using it or suggest alternatives. However, the context is clear that for creating a new document, this is the tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gawirable/office-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server