Skip to main content
Glama
Sign In
Copilot Desktop MCP

Copilot Desktop MCP

by avianhermana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Create Docx

create_docx

Generates a native Word (.docx) document from structured content blocks including headings, paragraphs, bullets, and tables.

Instructions

Create a native Word document (.docx). blocks is a list of structured content blocks:

  • {"type": "heading", "text": "...", "level": 1-3}

  • {"type": "paragraph", "text": "..."}

  • {"type": "bullets", "items": ["item 1", "item 2"]}

  • {"type": "table", "rows": [["Col 1", "Col 2"], ["Val 1", "Val 2"]]}

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": {
      "path": "<path>",
      "blocks": "<blocks>"
    },
    "name": "create_docx"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
titleNo
blocksYes
overwriteNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, yet it says nothing about overwrite semantics (the schema's overwrite flag defaults to false — does the call fail or silently replace?), directory/permission requirements, or any side-effect profile. The block-format detail is useful content guidance but does not disclose mutation behavior.

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?

One purpose sentence followed by a tight, scannable bullet list of block shapes; the format declaration is front-loaded and no sentence is redundant.

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 needn't be explained, and the block content format is well covered. But for a file-writing tool with no annotations, the absence of any statement about path requirements, title usage, or overwrite behavior leaves a real gap for correct invocation.

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 0%, and the description fully compensates for the hardest parameter by enumerating the exact block shapes and their fields — information available nowhere else in the structured data. However, it adds zero meaning for path, title, and overwrite, leaving three of four parameters undocumented.

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?

States a specific verb and resource ('Create a native Word document (.docx)'), and the explicit .docx format distinguishes it from create_pdf, create_excel, and create_pptx without needing to inspect any schema.

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 guidance: nothing says when to pick this over create_pdf or read_document, no prerequisites are given, and no mention of what happens if the target file already exists. Only the implied 'you want a .docx' condition is present.

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