Skip to main content
Glama
KitchenSink4AI

io.github.nometalalchemist/kitchensink4xl

by KitchenSink4AI
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

copy_workbook

Copy an Excel workbook byte-for-byte to a new path, preserving charts, macros, and queries. Existing files stay untouched unless overwrite is enabled; a backup is created first for restore.

Instructions

Copy a workbook file byte-for-byte from src to dst, so nothing in the original is re-serialized or degraded (charts, shapes, macros, and queries all carry over intact). An existing dst is left untouched unless overwrite is true, in which case dst is FIRST rotated into its .ks4xl-backups prev slot and then replaced (restore source='prev' brings it back). Returns the destination path. Use this to branch a working copy before a risky batch of edits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dstYes
srcYes
overwriteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

With only readOnlyHint=false in annotations, the description carries the behavioral burden and excels: it explains the byte-for-byte guarantee, the overwrite flow with backup rotation into .ks4xl-backups, the restore path via source='prev', and the return value. This gives the agent a precise model of side effects and safety.

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 dense yet efficient. Each sentence earns its place: the preservation guarantee, the overwrite/backup behavior, the return value, and the recommended use case. It is front-loaded with the core purpose and avoids filler.

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?

Despite having no output schema, the description states the return value ('Returns the destination path'). It also covers the key edge case (overwrite) and the typical use scenario. For a 3-parameter copy tool, nothing essential is missing.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate. It does: 'from src to dst' clarifies both parameters as source and destination paths, and overwrite semantics are fully described including backup rotation and restore behavior. The only minor gap is not explicitly stating that src/dst are file paths, though 'destination path' appears in the return value.

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 states a specific verb and resource: 'Copy a workbook file byte-for-byte from src to dst.' It further distinguishes itself from sibling tools by emphasizing whole-file preservation and the branch-before-edits use case, which clearly separates it from copy_range or create_workbook.

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

Usage Guidelines4/5

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

The description explicitly recommends using this tool 'to branch a working copy before a risky batch of edits,' providing clear context. It does not explicitly name alternatives or state when not to use it, but the 'byte-for-byte whole workbook' framing strongly implies the boundary against range-level or create operations.

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