Skip to main content
Glama
Sign In
office-mcp-server

office-mcp-server

by jiahuidegit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

word_create

Create a new Word document with your specified title, author, and output path. Choose from multiple templates and themes to generate documents suited to your needs.

Instructions

创建一个新的 Word 文档

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": {
      "title": "<title>",
      "outputPath": "<outputPath>"
    },
    "name": "word_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
themeNo主题风格
titleYes文档标题
authorNo作者
templateNo使用的模板类型
outputPathYes输出路径

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

B3.2/5.0
Behavior2/5

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

The description adds no behavioral detail beyond 'create new document'. Annotations indicate it is not read-only and not destructive, but nothing is said about overwriting existing files, file format specifics, or side effects. There is no contradiction with annotations, but also no added transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that fully states the tool's purpose without unnecessary words. It is front-loaded and easily scannable.

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?

With five parameters, two enums, and no output schema, the description is too minimal. It does not explain behavioral specifics like whether the document is saved immediately, how templates/theme affect output, or what happens if the output file already exists. This leaves the agent with questions beyond what the schema provides.

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 (theme, title, author, template, outputPath) already have descriptions in the schema. The tool description does not add any parameter semantics, but it doesn't need to given the schema's completeness.

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?

The description clearly states it creates a new Word document, which is a specific verb+resource action. It distinguishes itself from sibling tools like excel_create and word_add_* which either create a different file type or modify 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 Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The sibling tool names imply this is for creating new documents, but the description does not explicitly state when to use it or when to avoid it.

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