Skip to main content
Glama

sassy_untar

DestructiveIdempotent

Extracts tar, tar.gz, tar.bz2, and tar.xz archives with a data-only filter, writing files to disk; destination defaults to the archive's parent folder with the .tar extension removed.

Instructions

Mutating: writes extracted files to disk. Extracts tar, tar.gz, tar.bz2, or tar.xz archives using a data-only extraction filter. destination defaults to the archive's parent directory under the archive name with the .tar extension removed. Existing files at the destination are silently overwritten. There is no password option, unlike sassy_unzip. Returns the extraction path, the file count, and a sample of the first 20 member names. Use it to open archives created by sassy_tar or downloaded from the web.

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_untar"
  }
}

Input Schema

NameRequiredDescriptionDefault
archiveYes
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_untarOutput"New value: +"sassy_untarDictOutput"
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that existing files at the destination are silently overwritten, that a data-only extraction filter is applied, that there is no password support, and how the default destination is derived. Annotations already flag destructive/idempotent, and the description supplies the operational consequences an agent needs before invoking it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The mutating warning is front-loaded and each sentence adds a distinct fact (formats, destination default, overwrite behavior, return shape, intended use). It is dense but well ordered, with no filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers safety consequences, destination semantics, supported formats, and even the return payload despite an output schema existing. The one slightly opaque element is the phrase 'data-only extraction filter,' which is not explained in terms of what metadata or permissions are dropped.

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 description coverage is 0%, so the description must carry the parameters, and it does explain the destination default precisely (archive's parent directory, archive name minus .tar). The archive parameter is left self-evident by name, which is a minor but tolerable gap.

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?

States a specific verb and resource ("Extracts tar, tar.gz, tar.bz2, or tar.xz archives") and enumerates exactly which formats are supported. It also distinguishes itself from the sibling sassy_unzip by noting the absence of a password option.

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 archives created by sassy_tar or downloaded from the web" gives a clear usage context, and the comment about sassy_unzip implicitly routes password-protected archives elsewhere. It stops short of an explicit 'use sassy_unzip when X' statement, so the alternative routing must be inferred.

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