Skip to main content
Glama

excel_delete_sheet

Destructive

Remove a specified sheet from an Excel workbook. Optionally create a backup before removal to prevent data loss.

Instructions

Delete a sheet from the workbook

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesPath to the Excel file
sheetNameYesName of the sheet to delete
createBackupNo
Behavior2/5

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

The annotations already declare destructiveHint=true, indicating the tool is destructive. The description adds no further behavioral context, such as irreversibility, the effect on formulas, or the backup option. Without additional disclosure, the agent may miss important constraints.

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?

Single sentence, no wasted words. Clearly front-loaded with the action. However, it could be slightly more informative without sacrificing conciseness.

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?

No output schema, and the description omits important details like the effect of the createBackup parameter or whether the deletion is irreversible. For a destructive operation, more context is needed to ensure appropriate use.

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 description coverage is 67% (filePath and sheetName have descriptions, createBackup does not). The tool description does not mention any parameters or add meaning beyond the schema, so it provides no value for parameter understanding.

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?

The description 'Delete a sheet from the workbook' is a specific verb+resource, clearly indicating the action and target. It distinguishes from sibling tools like excel_create_sheet or excel_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 this tool versus alternatives. No mention of prerequisites, such as checking if the sheet exists or handling of the last sheet. Implicitly, it's used to delete a sheet, but no context is provided.

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