Skip to main content
Glama
rcarmo

office-document-mcp-server

by rcarmo
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

office_comment

Add, retrieve, reply to, or delete comments in Word, Excel, and PowerPoint documents. Supports targeting specific cells, text, slides, or comment IDs.

Instructions

Manage comments in Word, Excel, or PowerPoint documents.

Replaces: excel_add_comment, excel_get_comments, word_add_comment, pptx_add_comment, pptx_get_comments

Examples: # Get all comments from Excel office_comment(file_path="data.xlsx", operation="get")

# Add comment to Excel cell
office_comment(
    file_path="data.xlsx",
    operation="add",
    target="B5",
    text="Review this value"
)

# Add comment to Word text
office_comment(
    file_path="report.docx",
    operation="add",
    target="project timeline",
    text="Verify dates with PM"
)

# Reply to an existing Word comment by comment ID
office_comment(
    file_path="report.docx",
    operation="reply",
    target="12",  # comment ID from office_comment(..., operation="get")
    text="Acknowledged - updated in v2"
)

# Add comment to PowerPoint slide
office_comment(
    file_path="deck.pptx",
    operation="add",
    target="3",  # or "slide:3"
    text="Update chart data"
)

Args: file_path: Path to the document operation: add/get/reply/delete plus resolve/reopen for Word target: Target location/ID - Excel add/delete: cell reference (e.g., "B5") - Excel get: optional sheet name filter - Word add: text span to annotate - Word reply/resolve/reopen/delete: comment ID - PowerPoint add: slide number ("3" or "slide:3") - PowerPoint delete: "slide:N" or "slide:N/comment:I" text: Comment text (required for add/reply) author: Author display name. Also used by Word get(filter="mine") output_path: Optional output path (defaults to overwriting input) format: For Word get only: "flat" (default) or "threaded" filter: For Word get only: "all" (default), "open", "resolved", "mine"

Returns: Dictionary with operation results

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYesPath to the document
operationNoadd/get/reply/delete plus resolve/reopen for Word
targetNoTarget location/ID
textYesComment text (required for add/reply)
authorNoAuthor display name. Also used by Word get(filter="mine")
output_pathNoOptional output path (defaults to overwriting input)
formatNoFor Word get only: "flat" (default) or "threaded"
filterNoFor Word get only: "all" (default), "open", "resolved", "mine"

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

Annotations provide readOnlyHint=false and destructiveHint=false; the description adds behavioral context such as operation-specific behavior per app (e.g., resolve/reopen for Word only), target variations, and default output overwrite. No contradictions.

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?

The description is lengthy but well-structured with examples and separate sections for Args and Returns. The main purpose is front-loaded. Could be slightly more concise, but clarity benefits from examples.

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

Completeness5/5

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

All 8 parameters are described with usage details. Despite no output schema, the description states return type ('dictionary'). Covers all operations and supported apps comprehensively.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. The description adds meaning beyond schema by detailing target usage per operation/app and providing concrete examples (e.g., 'target' for Excel add is a cell reference, for Word add is a text span).

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 explicitly states 'Manage comments in Word, Excel, or PowerPoint documents.' It lists specific operations and replaces several sibling tools (e.g., excel_add_comment, word_get_comments), clearly distinguishing its unified functionality.

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?

The description provides detailed examples for each operation and app, explaining how target varies. It mentions replaced tools but does not explicitly state when to avoid this tool in favor of others for non-comment tasks (e.g., reading content via office_read).

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