Skip to main content
Glama
Sign In
Excel MCP Server

Excel MCP Server

by mort-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

copy_sheet

Copy a worksheet inside an Excel workbook by providing the source sheet name and a new name for the copy.

Instructions

Copy a worksheet within 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>",
      "source_sheet": "<source_sheet>",
      "new_name": "<new_name>"
    },
    "name": "copy_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
workbook_pathYesPath to the Excel workbook
source_sheetYesName of the worksheet to copy
new_nameYesName for the copied worksheet

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Without annotations, the description must disclose behavioral traits. It only states 'copy' but does not mention whether formatting is preserved, if the workbook must be closed, or other effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise, but it is too brief to be adequately informative. It could include more context while remaining short.

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?

With no annotations, no output schema, and a simple description, the tool's behavior is under-specified. For a mutation tool, more details about side effects and requirements are needed.

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 100%, so description adds no extra meaning beyond parameter names. Baseline 3 is appropriate as it does not clarify constraints like allowed characters for new_name.

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 (copy) and resource (worksheet) with scope (within the workbook), distinguishing it from sibling tools like create_sheet or rename_sheet.

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 copy_sheet vs alternatives like create_sheet for new sheets or rename_sheet for renaming. The agent is left 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