Skip to main content
Glama
haris-musa

Excel MCP Server

by haris-musa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Create workbook

create_workbook
Destructive

Create a new empty Excel workbook at a specified path, with optional sheet names and overwrite control.

Instructions

Create a new, empty Excel workbook.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
sheetsNoDefault: ['Sheet1'].
overwriteNoReplace an existing file (else an error).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv2.0.0
    • removedInput schema / properties / overwrite / default
      Removed value: -false
    • changedInput schema / properties / overwrite / description
      Previous value: -"Replace the file if it already exists."New value: +"Replace an existing file (else an error)."
    • removedInput schema / properties / overwrite / title
      Removed value: -"Overwrite"
    • removedInput schema / properties / path / description
      Removed value: -"Path to an .xlsx, .xlsm, .xltx or .xltm file. Relative paths are resolved in the server's workbook directory when one is configured; otherwise use an absolute path."
    • removedInput schema / properties / path / title
      Removed value: -"Path"
    • removedInput schema / properties / sheets / anyOf
      Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "minItems": 1,
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / sheets / default
      Removed value: -null
    • changedInput schema / properties / sheets / description
      Previous value: -"Worksheet names, in order. Default: ['Sheet1']."New value: +"Default: ['Sheet1']."
    • addedInput schema / properties / sheets / items
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / sheets / minItems
      Added value: +1
    • removedInput schema / properties / sheets / title
      Removed value: -"Sheets"
    • addedInput schema / properties / sheets / type
      Added value: +"array"
    • removedInput schema / title
      Removed value: -"create_workbookArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "create_workbookOutput",
-  "type": "object"
-}New value: +null
  2. Changed5 schema fields changedv1.1.1
    • removedInput schema / properties / filepath
      Removed value: -{
-  "title": "Filepath",
-  "type": "string"
-}
    • addedInput schema / properties / overwrite
      Added value: +{
+  "default": false,
+  "description": "Replace the file if it already exists.",
+  "title": "Overwrite",
+  "type": "boolean"
+}
    • addedInput schema / properties / path
      Added value: +{
+  "description": "Path to an .xlsx, .xlsm, .xltx or .xltm file. Relative paths are resolved in the server's workbook directory when one is configured; otherwise use an absolute path.",
+  "title": "Path",
+  "type": "string"
+}
    • addedInput schema / properties / sheets
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "minItems": 1,
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Worksheet names, in order. Default: ['Sheet1'].",
+  "title": "Sheets"
+}
    • changedInput schema / required
      Previous value: -[
-  "filepath"
-]New value: +[
+  "path"
+]
  3. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=false. The description adds little beyond this: it does not explain overwrite behavior, file-system side effects, or what happens if the path already exists.

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?

A single front-loaded sentence with no wasted words. It is appropriately sized for a simple creation tool.

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?

For a simple creation tool with annotations covering safety and schema covering most parameters, the description is minimally sufficient to convey the core operation. However, it omits usage guidance and any explanation of the required path parameter, so an agent must rely entirely on structured fields.

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

Parameters2/5

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

Schema description coverage is 67%, with 'path' undocumented in both schema and description. The description provides no parameter meaning, so it fails to compensate for the undocumented required parameter.

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 gives a specific verb and resource: 'Create a new, empty Excel workbook.' It distinguishes the operation from siblings such as import_workbook and create_sheet by emphasizing a new, empty workbook file.

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?

There is no guidance on when to use this tool versus alternatives like import_workbook, create_sheet, or list_workbooks. The description states only what it does, leaving the agent to infer usage context.

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