delete_sheet
Delete a sheet by providing its unique ID to remove it from the document platform.
Instructions
シート削除
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | シートID |
Delete a sheet by providing its unique ID to remove it from the document platform.
シート削除
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | シートID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description carries full burden. It fails to disclose critical behavioral traits such as irreversibility, required permissions, effects on related data, or whether deletion is soft or hard.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short but underspecified, not concise in a helpful sense. It fails to communicate essential information in the space available.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a deletion tool with no annotations or output schema, the description is incomplete. Missing information on return value, side effects, user confirmation, or error conditions. Siblings provide context but the description itself is inadequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% with clear 'Sheet ID' description for the only parameter. The tool description adds no additional semantic value beyond the schema, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description 'シート削除' is a tautology restating the tool name 'delete_sheet'. It lacks any additional context to distinguish from siblings. The verb 'delete' is implied by the name, so purpose is clear but not elaborated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 like 'remove_column' or 'update_sheet'. No prerequisites, exclusions, or context for appropriate use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/asicojp/sparksheets-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server