Skip to main content
Glama

excel_copy_range

Destructive

Copies a specified range from one Excel sheet to another location within the same workbook.

Instructions

Copy range to another location

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesPath to the Excel file
sourceSheetNameYesSource sheet name
sourceRangeYesSource range (e.g., A1:D10)
targetSheetNameYesTarget sheet name
targetCellYesTop-left cell of destination
createBackupNo
Behavior2/5

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

The annotation destructiveHint: true indicates the tool modifies the workbook, but the description adds no further behavioral context. It does not disclose whether the copy includes formatting, what happens to existing data in the target range, or whether a backup is created (despite the createBackup parameter).

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 concise sentence, but it lacks structure for a tool with 6 parameters and a destructiveHint. While front-loaded, it omits important details such as parameter behavior, making it under-specified for effective use.

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?

Given the tool's complexity (6 parameters, destructive, no output schema), the description is incomplete. It does not explain the copy behavior (e.g., values only vs formatting), the effect on the target range, or what the tool returns upon completion.

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?

With 83% schema description coverage, the input schema already documents most parameters. The description 'Copy range to another location' adds no additional parameter-level context, so it neither improves nor reduces the baseline understanding. A score of 3 reflects adequate but not enhanced parameter semantics.

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 'Copy range to another location' clearly states the purpose of copying a range of cells within an Excel file. However, it does not differentiate from sibling tools like excel_duplicate_sheet (which copies an entire sheet) or explain the scope (same workbook only).

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?

The description provides no guidance on when to use this tool versus alternatives such as excel_write_range or excel_read_range. It does not mention prerequisites, potential overwrites, or any exclusion conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sbraind/excel-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server