Skip to main content
Glama
Sign In
Excel MCP Server

Excel MCP Server

by haris-musa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Copy sheet

copy_sheet

Duplicate an Excel worksheet to the end of a workbook, keeping all content; tables get new names while PivotTables share source data.

Instructions

Copy a worksheet to a new last sheet, with everything on it, as Excel does. Self-references point at the copy; tables get new names (Sales2); PivotTables share the original's data.

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": {
      "path": "<path>",
      "sheet": "<sheet>",
      "new_name": "<new_name>"
    },
    "name": "copy_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
sheetYes
new_nameYes1-31 characters, none of [ ] : * ? / \.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.0.0
    • changedInput schema / properties / new_name / description
      Previous value: -"New sheet name: 1-31 characters, none of [ ] : * ? / \\."New value: +"1-31 characters, none of [ ] : * ? / \\."
    • removedInput schema / properties / new_name / title
      Removed value: -"New Name"
    • 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 / sheet / description
      Removed value: -"Worksheet name, e.g. 'Sheet1'."
    • removedInput schema / properties / sheet / title
      Removed value: -"Sheet"
    • removedInput schema / title
      Removed value: -"copy_sheetArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "copy_sheetOutput",
-  "type": "object"
-}New value: +null
  2. Addedv1.1.1

TDQS

A4.1/5.0
Behavior5/5

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

Goes well past the annotations, which only declare non-readonly/non-destructive/non-idempotent. It discloses what actually happens to the copied content: self-references rebind to the copy, tables are renamed (Sales2), and PivotTables share the original's data — exactly the surprises an agent would otherwise hit.

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 tight sentences, front-loaded with the core operation and then the edge-case behavior, with no filler or restatement of the title.

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

Completeness4/5

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

For a content-copying operation the description covers the behavioral nuances that matter most, and the annotations cover safety. It falls slightly short on inputs (two undocumented params) and there is no output schema, so the caller gets no hint of what the tool returns.

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 only 33% (just new_name is documented), and the description does not compensate: path and sheet are never explained, and new_name is only obliquely implied by 'a new last sheet'. With low coverage the description should carry more of the parameter burden than it does.

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 ('Copy a worksheet to a new last sheet, with everything on it'), including where the copy lands. This clearly separates it from siblings like create_sheet (blank sheet), rename_sheet, and copy_range (range-level copy).

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 is implied by the operation ('as Excel does'), so an agent can infer this is the sheet-duplication path, but there is no explicit when-to-use or when-not guidance and no sibling is named as an alternative. Nothing misleading, but nothing routes the agent either.

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