Skip to main content
Glama
rcarmo

office-document-mcp-server

by rcarmo

office_table

Manage tables in Word, Excel, and PowerPoint: retrieve data, add rows, update cells, or create new tables.

Instructions

Manage tables in Word, Excel, or PowerPoint documents.

Replaces: excel_get_table, excel_append_table_row, excel_update_table_row, word_get_table, word_insert_table_row, word_patch_table_row, word_create_new_table, pptx_get_table, pptx_insert_table_row, pptx_patch_table_cell

Examples: # Get Excel table data office_table(file_path="data.xlsx", operation="get", table_id="Sales")

# Add row to Excel table
office_table(
    file_path="data.xlsx",
    operation="add_row",
    table_id="Sales",
    data={"Product": "Widget", "Amount": 100}
)

# Update Excel table row
office_table(
    file_path="data.xlsx",
    operation="update_row",
    table_id="Sales",
    row_index=2,
    data={"Amount": 150}
)

# Get Word table (by index, passed as string)
office_table(file_path="report.docx", operation="get", table_id="0")

# Create Word table
office_table(
    file_path="report.docx",
    operation="create",
    data={
        "headers": ["Phase", "Owner", "Target Date"],
        "rows": [{"Phase": "Discovery", "Owner": "PM", "Target Date": "2026-04-01"}],
        "insert_after_section": "Delivery Plan"
    }
)

# Get PowerPoint table (slide number as string)
office_table(file_path="deck.pptx", operation="get", table_id="3")

Args: file_path: Path to the document operation: "get" to retrieve table data, "add_row" to append a row, "update_row" to modify an existing row, or "create" to create a new table (Word and PowerPoint) table_id: Table identifier as a string. For Excel pass the table name (e.g. "Sales"). For Word pass the 0-based table index for get/add/update (e.g. "0"). For PowerPoint pass the slide number (e.g. "3"). For Word create, table_id is optional. data: Row data as a dict with column names or indices as keys and cell values as values. Required for add_row and update_row. For Word create, provide an object with "headers" and optional "rows", "insert_after_section", "insert_before_section", "output_path", and "author". For PowerPoint update_row include "row", "col", and "value" keys. row_index: 1-based row index for update_row operations

Returns: Dictionary with table data or operation result

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYesPath to the document
operationNo"get" to retrieve table data, "add_row" to append a row, "update_row" to modify an existing row, or "create" to create a new table (Word and PowerPoint)
table_idNoTable identifier as a string. For Excel pass the table name (e.g. "Sales"). For Word pass the 0-based table index for get/add/update (e.g. "0"). For PowerPoint pass the slide number (e.g. "3"). For Word create, table_id is optional.
dataYesRow data as a dict with column names or indices as keys and cell values as values. Required for add_row and update_row. For Word create, provide an object with "headers" and optional "rows", "insert_after_section", "insert_before_section", "output_path", and "author". For PowerPoint update_row include "row", "col", and "value" keys.
row_indexNo1-based row index for update_row operations
output_pathNo
modeNo
Behavior4/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds value by detailing per-operation behavior (e.g., create requires specific data structure, update_row uses row_index). It does not contradict annotations. However, it does not mention side effects like overwriting or undo, but given the annotation coverage, this is sufficient.

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 well-structured with intro, replaced tools list, examples, and args section. It is somewhat long but justified by the tool's complexity (multiple apps and operations). Front-loads the core purpose and examples. Could be slightly more concise, but the format aids readability.

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?

Given the tool's complexity (7 parameters, multiple app-specific behaviors, no output schema), the description covers inputs and return value adequately. It lacks error handling or permission notes, but sibling tools and annotations fill some gaps. The replaced tools list provides context for migration. Overall, a solid description.

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 71%, and the description explains parameters with context beyond the schema, especially table_id (per-app details) and data (nested structure for create). However, output_path and mode are present in schema but not described in the description. Examples help clarify usage, so overall good but not complete.

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 the tool manages tables in Word, Excel, or PowerPoint documents. It lists replaced tools (e.g., excel_get_table, word_get_table), which distinguishes it from siblings. The verb 'manage' along with examples for get, add_row, update_row, create operations makes the purpose specific and actionable.

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 extensive examples for each operation and app, showing exactly how to use the tool. It lists replaced tools, implying when to use this instead. However, it does not explicitly contrast with siblings like office_read or office_patch, nor does it state when not to use this tool. The guidance is clear but could be more direct about alternatives.

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