Skip to main content
Glama
nometalalchemist

io.github.nometalalchemist/kitchensink4xl

manage_backups

List, restore, purge, or snapshot automatic Excel workbook backups from rotating prev and anchor slots, with dry-run purge and permanent dated snapshots.

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.0

TDQS

A5/5.0
Behavior5/5

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

There are no annotations, so the description bears full responsibility for behavioral disclosure. It thoroughly covers destructive semantics: restore rotates current content into prev first so it is undoable, validates the payload, uses atomic replacement, and refuses when files are open in Excel. It also explains dry_run defaults to TRUE and that snapshots are never rotated.

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 long but dense and well-structured. Each sentence earns its place by defining an action, a parameter, or a safety behavior. It opens with the core resource and slot model, then enumerates actions in consistent action='x' format, and closes with the limitation and recovery pointer. Nothing feels like 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?

For an eight-parameter tool with no annotations and no schema-level descriptions, the description is remarkably complete. It covers rotation semantics, restore undo behavior, Excel-open refusal, dry_run behavior, snapshot permanence, the limitation of prev, and the recovery alternative. Since an output schema exists, failing to describe return values is acceptable.

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 compensate fully. It does: action values are defined, path versus directory is distinguished, source is constrained to prev/anchor, scope is constrained to orphans/slots, dry_run's default and meaning are stated, and label/dest_dir are explained for snapshots. Every parameter receives meaningful semantic context.

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 names a specific resource (the hidden .ks4xl-backups folder) and enumerates four concrete actions: list, restore, purge, and snapshot. It also explains the two rotating slot types, prev and anchor, so an agent understands exactly what the tool manages and how it differs from ordinary workbook tools.

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 action-specific usage: list takes a path or directory, restore requires source prev/anchor and refuses open Excel files, purge accepts scopes orphans/slots, and snapshot creates permanent copies. It also names the alternative for lost/corrupt files: get_workflows task='recover-workbook'. This gives an agent clear conditions for selection.

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

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/nometalalchemist/KitchenSink4XL'

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