ReMCP

Edit spreadsheet

edit_spreadsheet

Destructive

Use this when the user needs to create a new XLSX workbook or directly edit XLSX cells/ranges/formulas without launching Excel. Set create=true only for a new path; it fails rather than overwriting an existing workbook. Prefer explicit cells/ranges and write to output when preserving an existing original matters.

Input Schema

Name	Required	Description
`path`	Yes	Existing .xlsx path, or the new workbook destination when create=true.
`edits`	Yes	Bounded list of spreadsheet edits; each item names a cell/range and the value(s) or formula to write.
`sheet`	No	Worksheet name. For create=true, defaults to Sheet1 and becomes the new workbook sheet name.
`create`	No	Create a new XLSX at path. Fails if path already exists; do not combine with output.
`device`	Yes	ReMCP device id returned by list_devices. Required for every device operation.
`output`	No	Optional output .xlsx when editing an existing workbook; defaults to replacing input.

Output Schema

Name	Required	Description	Default
`data`	No	Edit spreadsheet structured result for edit_spreadsheet. Stable fields are declared explicitly; platform-specific fields may be added. Large results may return truncated/bytes/preview instead of the full payload.
`text`	Yes	Concise human-readable result of the tool call.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 19, 2026
RemovedSep 21, 2026

Changed5 schema fields changedSep 21, 2026

addedInput schema / properties / create

Added value: +{
+  "description": "Create a new XLSX at path. Fails if path already exists; do not combine with output.",
+  "type": "boolean"
+}

changedInput schema / properties / output / description

Previous value: -"Optional output .xlsx; defaults to replacing input."New value: +"Optional output .xlsx when editing an existing workbook; defaults to replacing input."

changedInput schema / properties / path / description

Previous value: -"Input .xlsx path."New value: +"Existing .xlsx path, or the new workbook destination when create=true."

changedInput schema / properties / sheet / description

Previous value: -"Worksheet name."New value: +"Worksheet name. For create=true, defaults to Sheet1 and becomes the new workbook sheet name."

addedOutput schema / properties / data / properties / created
```
Added value: +{
+  "type": "boolean"
+}
```

First observedSep 21, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description goes beyond the annotations by clarifying that create=true fails rather than overwriting an existing workbook, and that using output preserves the original file. This meaningfully complements destructiveHint=true and explains what could be destroyed or preserved.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each adding distinct value: the core use case, the create=true guardrail, and the output-preservation guidance. No filler or redundancy.

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?

The tool has a full input schema and an output schema, and the description covers the critical caveats: create-only semantics, rejection of overwrites, and output preservation. Nothing essential for correct invocation is missing.

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 description coverage is 100%, so the input schema already documents all parameters. The description adds useful context about create=true and output, but it does not need to restate parameter details, keeping it at the baseline.

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 opens with a specific verb and resource: creating an XLSX workbook or editing XLSX cells/ranges/formulas. It also distinguishes itself from launching Excel, making its purpose unambiguous relative to siblings like edit_document or launch_app.

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 explicitly states when to use the tool ('Use this when the user needs to create a new XLSX workbook or directly edit XLSX cells/ranges/formulas without launching Excel'). It adds practical guardrails about create=true and when to use output, though it does not name alternative tools for non-XLSX editing.

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

All ReMCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?