Skip to main content
Glama
rcarmo

office-document-mcp-server

by rcarmo

word_create_sow_from_markdown

Creates a Statement of Work document by extracting structured data from Markdown and filling a corporate-styled .docx template.

Instructions

Create a SOW document from inline markdown or markdown_file by filling a template.

    IMPORTANT: This tool requires a template to preserve document structure,
    formatting, and corporate styling. It extracts data from Markdown and
    uses generate_sow to fill the template.

    Workflow:
    1. Parse the Markdown to extract structured SOW data
    2. Load the template document
    3. Fill placeholders and tables with extracted data
    4. Save the result

    Example:
        create_sow_from_markdown(
            output_path="04. Artifacts/contoso-sow.docx",
            template_path=".github/skills/statement-of-work/templates/Agile.docx",
            markdown='''

Contoso – Cloud Migration – Statement of Work

1. Engagement Overview

Customer: Contoso Ltd Provider: Microsoft Project: Cloud Migration Sprint 1

1.1 Business Objectives

Objective

Activities

Assumptions

Migrate 15 apps

Assessment, planning

Apps are containerizable

'''

        )

    Args:
        output_path: Path for the output .docx file
        template_path: Path to the .docx template (REQUIRED)
        markdown: Markdown content of the SOW (inline)
        markdown_file: Optional path to a Markdown file. Use this for
            very large inputs to avoid MCP argument-size limits.

    Returns:
        Status dictionary with file path and extraction summary
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
output_pathYesPath for the output .docx file
markdownNoMarkdown content of the SOW (inline)
template_pathYesPath to the .docx template (REQUIRED)
markdown_fileNoOptional path to a Markdown file. Use this for very large inputs to avoid MCP argument-size limits.
modeNo
Behavior4/5

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

Annotations indicate it is not read-only or destructive. Description adds value by detailing the workflow (parse, load template, fill, save) and the use of generate_sow internally, which provides behavioral context beyond the annotation hints.

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?

Description is well-structured with front-loaded purpose, then important note, workflow, example, and args. It is slightly verbose but every sentence adds value; no wasted words.

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?

Covers purpose, workflow, parameter distinctions, and return value. However, it omits explanation of the mode parameter (best_effort, safe, strict, dry_run), which is a gap for a tool with no output schema and medium complexity.

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 covers 4 out of 5 parameters with descriptions, so baseline is 3. Description adds context for markdown vs markdown_file (large inputs) but does not explain the mode parameter, which has enum but no description in 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?

Description clearly states verb (Create), resource (SOW document), and method (from markdown, filling template). It distinguishes from sibling tools like word_from_markdown and word_generate_sow by specifying the requirement for a template and the internal workflow.

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?

Description explains the workflow and requirement for a template, and gives an example. It does not explicitly state when not to use this tool or name alternatives, but the context implies it is for SOW creation with templates, which is distinct from siblings.

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/rcarmo/python-office-mcp-server'

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