xlsx-tools-mcp

Overview Schema Source Related Servers Discussions Admin

create_sheet

Add an empty sheet to an existing Excel workbook, naming it and optionally placing it at a specific position or appending it.

Instructions

Add a new empty sheet to an existing workbook.

Args: path: Path to the .xlsx file, or the name of a preloaded file. Omit if only one file is configured. sheet: Name for the new sheet. index: Zero-based position to insert at; omit to append at the end.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	No
`index`	No
`sheet`	Yes
`backup`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.0Oct 4, 2026

addedInput schema / properties / backup

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Backup"
+}

First observedv0.1.0Aug 17, 2026

TDQS

B3.4/5.0

Behavior2/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 for a mutating tool. It does not say what happens if a sheet with that name already exists, whether the change is persisted to disk, what the backup parameter does, or whether the workbook must be closed — all meaningful behavioral gaps for a write operation.

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?

Front-loaded purpose with a compact, well-structured Args block; no filler sentences. Slight redundancy between the schema titles and the arg list, but nothing wasteful.

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?

An output schema exists so return values need not be described, and the per-parameter notes are helpful. However, for a mutation tool with zero annotations and an undocumented 'backup' parameter, the description leaves key behaviors (name collision, persistence) unaddressed.

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 coverage is 0%, so the description must compensate. It documents three of four parameters with added meaning (path accepts a preloaded file name; index is zero-based and defaults to append), which is genuinely useful, but leaves the 'backup' parameter completely unexplained.

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?

States a specific verb and resource ('Add a new empty sheet to an existing workbook') and the word 'empty' distinguishes it from siblings like copy_sheet and create_workbook. An agent can identify the operation without opening the schema.

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?

Usage context is implied by the phrase 'an existing workbook' and the arg note 'Omit if only one file is configured', but there is no explicit when-to-use vs. alternatives guidance (e.g., copy_sheet when duplicating content, create_workbook when starting fresh).

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