Skip to main content
Glama
KitchenSink4AI

io.github.nometalalchemist/kitchensink4xl

by KitchenSink4AI
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

manage_backups

List, restore, purge, or snapshot Excel workbook backups stored in hidden .ks4xl-backups folders. Restores are validated and undoable, with dry-run purge reporting.

Instructions

Manage the automatic backups in the hidden .ks4xl-backups folder next to each mutated workbook: two rotating slots per file, prev (state before the most recent mutation) and anchor (session start). action='list': slot files with sizes and mtimes plus orphaned slot folders; give path for one workbook or directory for a folder. action='restore': overwrite path with source 'prev' or 'anchor'; the current content rotates into prev FIRST so a restore is itself undoable, the payload is validated as a real workbook before the atomic replace, and files open in Excel refuse. action='purge': delete backups; scope is 'orphans' (slot folders whose workbook is gone) or 'slots' (one workbook's pair); dry_run defaults to TRUE and only reports. action='snapshot': save a permanent DTG-stamped copy, YYYYMMDD_HHMM_, optional label and dest_dir; snapshots are never rotated and no purge scope touches them. LIMIT, stated loudly: prev holds the state before the LAST mutation this server made, so damage that lands AFTER the last save (crash, disk, another program) costs that final edit; only a snapshot habit covers it. Lost or corrupt file? get_workflows task='recover-workbook' is the walkthrough.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNo
labelNo
scopeNo
actionYes
sourceNo
dry_runNo
dest_dirNo
directoryNo

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

A5/5.0
Behavior5/5

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

Annotations only provide readOnlyHint=false, but the description discloses critical behavioral details beyond that: restore rotates current content into prev first so it is undoable, payloads are validated before atomic replace, Excel-open files refuse, dry_run defaults to TRUE and only reports, and snapshots are exempt from rotation and purge. It also candidly states the 'LIMIT' of prev coverage. This is excellent transparency.

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?

Although the description is dense, every sentence carries meaningful information: storage location, rotation slots, action semantics, safety behavior, default dry_run, limits, and routing to recovery. It is front-loaded with the core concept before diving into actions, and the 'LIMIT, stated loudly' section is a deliberate and effective structure for emphasizing the tool's coverage gap.

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?

Given the tool has 8 parameters, no output schema, no enums, and 0% schema coverage, this description is remarkably complete. It explains all actions, parameters, defaults, safety mechanisms, edge cases (orphans, Excel-open files), the rotation limit, and the correct sibling for recovery. Nothing essential for an agent to select and invoke this tool correctly is missing.

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 description coverage is 0%, so the description must explain all parameters, and it does. It maps path/directory for list, source for restore, scope for purge, dry_run, label, and dest_dir for snapshot. Each parameter's role is described in context, compensating fully for the empty schema descriptions.

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 clear verb and resource: 'Manage the automatic backups in the hidden .ks4xl-backups folder next to each mutated workbook.' It enumerates the four actions (list, restore, purge, snapshot) with concrete effects, and distinguishes itself from the recovery sibling by pointing to get_workflows task='recover-workbook' for lost/corrupt files. This is far more than a vague or tautological statement.

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?

The description gives explicit context for each action, including scope, source, dry_run behavior, and snapshot permanence. It also names the alternative tool and the exact condition for using it: 'Lost or corrupt file? get_workflows task=\"recover-workbook\" is the walkthrough.' This directly guides an agent on when not to use this tool.

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