Skip to main content
Glama
haris-musa

Excel MCP Server

by haris-musa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Create sheet

create_sheet

Add an empty worksheet to an existing Excel workbook, specifying its name and optional position.

Instructions

Add an empty worksheet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
new_nameYes1-31 characters, none of [ ] : * ? / \.
positionNo1-based. Default: last.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv2.0.0
    • addedInput schema / properties / new_name
      Added value: +{
+  "description": "1-31 characters, none of [ ] : * ? / \\.",
+  "type": "string"
+}
    • 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 / position / anyOf
      Removed value: -[
-  {
-    "minimum": 1,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / position / default
      Removed value: -null
    • changedInput schema / properties / position / description
      Previous value: -"1-based position. Default: after the last."New value: +"1-based. Default: last."
    • removedInput schema / properties / position / title
      Removed value: -"Position"
    • addedInput schema / properties / position / type
      Added value: +"integer"
    • removedInput schema / properties / sheet
      Removed value: -{
-  "description": "New sheet name: 1-31 characters, none of [ ] : * ? / \\.",
-  "title": "Sheet",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "path",
-  "sheet"
-]New value: +[
+  "path",
+  "new_name"
+]
    • removedInput schema / title
      Removed value: -"create_sheetArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "create_sheetOutput",
-  "type": "object"
-}New value: +null
  2. Addedv1.1.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish the safety profile (readOnly=false, destructive=false, idempotent=false). The description adds only that the new sheet is empty, but does not clarify that each call appends a distinct sheet, where it lands by default, or that no content is returned. With annotations covering safety, a 3 is fair.

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?

A single front-loaded sentence with zero filler. It is efficient, though arguably under-specified rather than purely concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter mutation tool with no output schema and an undescribed required 'path' parameter, the description is too thin. It omits parameter meaning, default placement behavior, and what the caller gets back.

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 coverage is 67%, and the description contributes nothing about the parameters. In particular the required 'path' has no schema description at all and is not explained in the description, so the agent gains no additional meaning here.

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?

States a specific verb (Add) and resource (empty worksheet), which is clear on its own and reasonably distinguishable from siblings like create_workbook or copy_sheet. However, it does not explicitly differentiate itself from those siblings in wording.

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 versus alternatives such as create_workbook (for a new file) or copy_sheet (to duplicate an existing one). No prerequisites or context for the sheet's placement are given.

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