Skip to main content
Glama

excel_write_range

Write a 2D list of values to an Excel sheet starting at a given cell, automatically extending the sheet's used range.

Instructions

Write a 2D list of values starting at start_cell.

The data is interpreted in row-major order: data[0][0] goes to start_cell, data[0][1] to the cell one column to the right, data[1][0] to the cell one row below, and so on. Writing extends the sheet's used range as needed (VAL-EXCEL-027).

Args: path: Path to an existing .xlsx. sheet: Name of the sheet. start_cell: Top-left cell of the write region (e.g. "A1"). data: 2D list of values. The empty list [] is accepted and is a no-op (the file is still saved; the workbook remains valid). folder: Optional base folder for relative paths.

Returns: {"ok": True}.

Raises: OfficeMCPError: ERR_FILE_NOT_FOUND if the file is missing, ERR_SHEET_NOT_FOUND for an unknown sheet, ERR_CELL_PARSE for a malformed start_cell, ERR_INVALID_PARAMS if data is not a list, ERR_UNSUPPORTED_FMT for non-.xlsx extensions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
sheetYes
start_cellYes
dataYes
folderNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: data interpretation in row-major order, extension of the used range, handling of empty list as no-op, and specific error types. This is comprehensive and beyond minimal requirements.

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 Args, Returns, and Raises sections. It is informative and front-loaded with the main action. While slightly verbose, every sentence serves a purpose, and it is appropriately sized for the complexity of the tool.

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?

Given the tool's complexity (five parameters, error handling, output schema existence), the description is complete. It covers all necessary aspects: parameters, behavior, return value, and error conditions. The output schema is mentioned indirectly, but the description does not need to detail it further.

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?

The description adds meaning to all five parameters beyond the input schema. It specifies that 'path' is for an existing .xlsx, 'sheet' is the sheet name, 'start_cell' is top-left like 'A1', 'data' is a 2D list, and 'folder' is optional for relative paths. This compensates for the 0% schema description coverage.

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 that the tool 'Write a 2D list of values starting at start_cell.' The verb 'Write' and resource 'excel range' are specific, and the explanation of row-major order distinguishes it from other tools like excel_write_cell or excel_read_sheet.

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 clear context for when to use this tool (writing a 2D array to an Excel range) but does not explicitly mention when not to use it or alternatives. The behavior is well explained, but no direct comparison to sibling tools.

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/gawirable/office-mcp'

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