SassyMCP

Official

Overview Schema Source Related Servers Discussions Admin

sassy_unzip

Idempotent

Extract .zip archives to a chosen destination with optional password support and zip-slip protection. Returns extraction path, file count, and sample entry names.

Instructions

Mutating: writes extracted files to disk. Extracts a .zip archive to destination, defaulting to the archive's parent directory under the archive's stem name. password (default empty) unlocks encrypted zips. Zip-slip protection rejects the whole archive with an error if any entry path escapes the destination. Existing files at the destination are silently overwritten. Returns the extraction path, the file count, and a sample of the first 20 entry names. Use it to open zips from any source; use sassy_zip to create archives for extraction with this tool.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`archive`	Yes
`password`	No
`destination`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.15.1Sep 18, 2026

addedOutput schema / additionalProperties
```
Added value: +true
```

removedOutput schema / properties

Removed value: -{
-  "result": {
-    "title": "Result",
-    "type": "string"
-  }
-}

removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```

changedOutput schema / title

Previous value: -"sassy_unzipOutput"New value: +"sassy_unzipDictOutput"

First observedv0.1.0Jul 31, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes far beyond the annotations by describing side effects (files written to disk, existing files silently overwritten), safety behavior (zip-slip protection rejects the whole archive), and return contents (path, file count, first 20 entry names). These details are consistent with readOnlyHint=false and add meaningful behavioral context the annotations do not provide.

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?

Four dense sentences pack the mutation warning, default destination behavior, password handling, zip-slip protection, overwrite semantics, returns, and sibling routing with no wasted words. The mutation warning is front-loaded, which is useful for an agent deciding whether to invoke the tool.

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?

Everything needed to call the tool correctly is present: required archive, optional destination default, optional password, overwrite behavior, security handling, and usage routing. Since an output schema exists, the description does not need to enumerate return values, and nothing else is missing for a correct invocation.

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?

The input schema has 0% description coverage, so the description carries the full burden of explaining parameters. It covers the archive to extract, the destination defaulting to the archive's parent under its stem name, and the password parameter defaulting to empty for encrypted archives, giving meaning to all three parameters.

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?

Begins with 'Mutating: writes extracted files to disk,' then clearly states it extracts a .zip archive to a destination with a defined default. The final sentence names sassy_zip as the archive-creation counterpart, so an agent can distinguish extraction from creation without needing to inspect schemas.

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?

Explicitly says 'Use it to open zips from any source; use sassy_zip to create archives for extraction with this tool,' giving both a usage context and a pointer to the relevant sibling. It does not explicitly contrast with the tar-extraction sibling sassy_untar, which is a minor gap in when-not-to-use guidance.

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

Deploy Server