Skip to main content
Glama
vocweb

synology-office-mcp

by vocweb

spreadsheet_delete_file

Permanently delete an entire .osheet spreadsheet file from Synology Office. Set confirm=true to execute; use drive_delete for non-spreadsheet files.

Instructions

WARNING: Permanently delete an ENTIRE spreadsheet file (.osheet). Different from spreadsheet_delete_sheet which removes only one tab inside a file. Uses the dedicated Spreadsheet API endpoint (Synology Office >= 3.7.0) and also evicts the file from the local name cache. For non-spreadsheet files use drive_delete. Provide either file_id or name; set confirm=true to execute.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_idNoAlphanumeric Spreadsheet ID (overrides name lookup).
nameNoSpreadsheet display name (resolved via local cache).
pathNoOptional Drive path to disambiguate same-name files.
confirmNoMust be true to actually delete.
Behavior5/5

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

No annotations, so description carries burden. It warns about permanence, mentions cache eviction, requires confirm flag, and notes API version requirement (Synology Office >= 3.7.0).

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?

Single, well-structured sentence with warning first, then key distinction, technical detail, and usage guidance. No wasted words.

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

Completeness5/5

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

For a destructive action with 4 params and no output schema, description covers purpose, alternatives, prerequisites, side effects, and technical requirements comprehensively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% description coverage; description adds mutual exclusivity of file_id/name, cache resolution for name, path disambiguation, and confirm requirement beyond schema defaults.

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 clearly states it deletes an entire spreadsheet file and explicitly distinguishes from spreadsheet_delete_sheet (deletes a tab) and drive_delete (for non-spreadsheet files).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance: use spreadsheet_delete_sheet for tab removal, drive_delete for non-spreadsheet files, and specifies to provide file_id or name with confirm=true to execute.

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/vocweb/synology-mcp-server'

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