Skip to main content
Glama
Sign In
Excel MCP Server

Excel MCP Server

by mort-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

write_cell

Write a value to a specific cell in an Excel workbook by providing the workbook path, sheet name, and cell reference.

Instructions

Write a value to a specific cell.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workbook_path": "<workbook_path>",
      "sheet_name": "<sheet_name>",
      "cell": "<cell>",
      "value": "<value>"
    },
    "name": "write_cell"
  }
}

Input Schema

NameRequiredDescriptionDefault
workbook_pathYesPath to the Excel workbook
sheet_nameYesName of the worksheet
cellYesCell reference (e.g., 'A1', 'B10')
valueYesValue to write (string, number, boolean, etc.)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description must disclose behavior. It fails to mention that the operation overwrites existing content, triggers recalculation, or handles type coercion. Lacks details on side effects.

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?

Single sentence, no fluff. Could be slightly expanded without losing conciseness, but current length is appropriate for a straightforward operation.

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?

Given high schema coverage and existence of output schema, description still lacks context like overwriting behavior and return value expectations. Adequate but not comprehensive.

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 has 100% description coverage, so baseline is acceptable. The description adds no additional meaning beyond parameter names. It does not explain valid formats for cell or value, but schema already does.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (write) and resource (value to a specific cell). It distinguishes from siblings like read_cell (read vs write) and write_range (specific cell vs range), though could more explicitly contrast.

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

Usage Guidelines2/5

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

No guidance on when to use write_cell versus alternatives like write_range or write_formula. Does not specify prerequisites or typical use cases.

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

Deploy Server

Other Tools