office_docs_mcp

Overview Schema Source Related Servers Discussions Admin

excel_write_cell

Write values, numbers, booleans, or formulas to any Excel cell by specifying file, sheet, and coordinate. Optionally create a backup before modifying.

Instructions

Write a value to a specific cell (e.g. 'A1', 'C10') in an Excel sheet.

Args:
    file_path: Path to the Excel file.
    sheet_name: Target sheet name.
    coordinate: Cell coordinate (e.g., 'A1', 'B5').
    value: The value to write (string, number, boolean, or formula like '=SUM(A1:A5)').
    backup: If True, create a backup of the original file before modifying.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`value`	Yes
`backup`	No
`file_path`	Yes
`coordinate`	Yes
`sheet_name`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Sep 27, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses the backup option and that values can be formulas, which is useful. However, it does not mention overwriting behavior, error handling for missing files/sheets, or other side effects, leaving significant behavioral gaps for a mutation tool.

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 concise and well-structured, with a one-sentence summary followed by a clear Args list. Each line earns its place, providing necessary parameter details without redundancy. Slightly verbose in repeating 'path to the Excel file' but overall efficient.

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?

The description covers parameters well but omits prerequisites such as the file must already exist (sibling excel_create_workbook implies this) and whether the target sheet must exist. Since output schema exists, return values need not be described, but without annotations, these operational constraints leave the tool incomplete for an agent to use correctly.

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

Parameters5/5

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

Despite 0% schema description coverage, the description fully explains each parameter: file_path, sheet_name, coordinate (with format examples), value (with allowed types including formulas), and backup (with its purpose). This adds substantial meaning beyond the schema's bare property names and types.

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 action (write a value) and the specific resource (a specific cell in an Excel sheet), with examples like 'A1' and 'C10'. It differentiates from siblings such as excel_write_range and excel_append_rows by focusing on a single cell, making its purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies usage for single-cell writes via the phrase 'specific cell' and gives an example, but it does not explicitly mention alternatives or when not to use this tool. Without guidance on alternatives like excel_write_range for ranges, the usage is only implied, not clearly specified.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.