Skip to main content
Glama

sassy_unzip

DestructiveIdempotent

Extract ZIP archives to a chosen destination, including password-protected files, while blocking zip-slip path escapes and overwriting existing files.

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.

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": {
      "archive": "<archive>"
    },
    "name": "sassy_unzip"
  }
}

Input Schema

NameRequiredDescriptionDefault
archiveYes
passwordNo
destinationNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.15.1
    • 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"
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, but the description adds the operational consequences: 'Existing files at the destination are silently overwritten' and 'Zip-slip protection rejects the whole archive with an error if any entry path escapes.' Those are exactly the failure modes and data-loss risks an agent needs before invoking a destructive write.

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?

Roughly four sentences, front-loaded with the mutating warning and then the action, defaults, hazards, and return shape in that order. Every clause conveys distinct operational information with no restatement of the name or title.

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 a three-parameter destructive tool, the description covers the action, defaults, overwrite hazard, security rejection behavior, and even a summary of return values — more than needed given an output schema exists. There is no meaningful gap an agent would hit while calling this tool.

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 carries the full burden, and it does: it explains the destination default (archive's parent directory under the stem name), the password default (empty, needed for encrypted zips), and that archive determines both the source and the default output path. All three parameters gain meaning not present in the bare schema.

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 opens with a specific verb and resource ('Extracts a .zip archive') and adds the mutation qualifier up front. It distinguishes itself from sassy_zip by naming the opposite operation (create vs. extract), so an agent can choose without opening either schema.

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?

'Use it to open zips from any source; use sassy_zip to create archives for extraction with this tool' explicitly routes the agent to the sibling and states the inverse use case. What's missing is an exclusion — e.g. which formats are unsupported, or whether it handles anything besides .zip — but the when-to-use guidance is clear.

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

Deploy Server

Other Tools