synology-office-mcp

spreadsheet_batch_update

Insert or delete rows or columns in a Synology Spreadsheet by providing sheet ID, start index, and count.

Instructions

Insert or delete rows/columns in a Synology Spreadsheet. Provide either file_id or name. Set confirm=true to execute.

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": {
      "sheet_id": "<sheet_id>",
      "action": "<action>",
      "index": "<index>",
      "count": "<count>"
    },
    "name": "spreadsheet_batch_update"
  }
}

Input Schema

Name	Required	Description
`file_id`	No	Alphanumeric Spreadsheet ID (overrides name lookup).
`name`	No	Spreadsheet display name (resolved via local cache).
`path`	No	Optional Drive path to disambiguate same-name files.
`sheet_id`	Yes	Internal ID of the sheet
`action`	Yes	Batch operation: insert or delete rows/columns
`index`	Yes	Starting row/column index (0-based)
`count`	Yes	Number of rows/columns to insert or delete
`confirm`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0May 26, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description must disclose behaviors. It mentions confirm=true to execute, implying a dry-run capability or two-step process, but does not explain what happens with confirm=false, whether changes are reversible, or required permissions for destructive operations.

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?

The description is two concise sentences, front-loaded with purpose, and includes essential usage hints without excess words.

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

Completeness3/5

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

Given no output schema, the description omits return value information. It covers basic usage but lacks details on error behavior, atomicity, and the meaning of confirm=false, which are important for an 8-parameter batch operation.

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 high (88%). The description adds minor value by noting 'confirm=true to execute' beyond the schema's default false, and clarifies the file_id/name choice. However, it does not elaborate on other parameters (path, sheet_id, index, count) beyond schema definitions.

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 the tool inserts or deletes rows/columns in a Synology Spreadsheet, with a specific verb and resource. It distinguishes from siblings like spreadsheet_append_rows and spreadsheet_write_cells by focusing on batch structural changes.

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 gives a hint about providing file_id/name and setting confirm=true to execute, but it does not clarify when to use this over other spreadsheet tools (e.g., when to insert rows vs. append rows) or any prerequisites like sheet existence.

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

Deploy Server