Skip to main content
Glama
Sign In
Excel MCP Server

Excel MCP Server

by mort-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

create_sheet

Create a new worksheet in an existing Excel workbook. Specify the workbook path, sheet name, and optional position for insertion.

Instructions

Create a new worksheet in the workbook.

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>"
    },
    "name": "create_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
workbook_pathYesPath to the Excel workbook
sheet_nameYesName for the new worksheet
indexNoOptional position to insert the sheet (0-based)

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 are provided, so the description carries full behavioral burden. It does not disclose side effects (e.g., overwriting an existing sheet?), permissions needed, or error conditions. The description only states the basic action without behavioral context.

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?

The description is a single, concise sentence with no wasted words. It is front-loaded with the core purpose. However, it could be slightly more structured by including parameter hints or usage notes without sacrificing brevity.

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 the output schema exists (so return values need not be explained) and schema coverage is full, the description minimally covers the tool's purpose. However, it lacks context about edge cases (e.g., duplicate sheet names), position handling, and integration with sibling tools, leaving gaps for complete understanding.

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 baseline is 3. The description adds no additional meaning beyond what the schema already provides for parameters like 'workbook_path', 'sheet_name', and 'index'. The optional 'index' parameter is not mentioned in the description.

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 ('Create') and the resource ('new worksheet in the workbook'). It distinguishes from siblings like copy_sheet or delete_sheet, though no explicit differentiation is provided. The verb and object are specific.

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 this tool versus alternatives (e.g., copy_sheet for duplication). No context about prerequisites, such as whether the workbook must exist or if sheet names must be unique. The agent would have to infer usage from the tool name alone.

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