Skip to main content
Glama

convert_archive

Compress files into archives or decompress and convert between gz, bz2, br, zip, tgz, tar, 7z, and rar formats; optionally list contents or extract to a directory.

Instructions

Compress/decompress archives. Input: gz, bz2, br, zip, tgz/tar.gz, tar.bz2, tar.xz, 7z, rar. Output: gz, br, zip, tgz. Supports listing contents.

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": {
      "inputPath": "<inputPath>",
      "outputPath": "<outputPath>"
    },
    "name": "convert_archive"
  }
}

Input Schema

NameRequiredDescriptionDefault
listOnlyNoOnly list archive contents without extracting (optional)
inputPathYesAbsolute path to input file or directory
extractDirNoDirectory to extract to (optional)
outputPathYesAbsolute path for output archive or extract directory
inputFormatNoInput format (auto-detected if not provided)
outputFormatNoOutput format (auto-detected if not provided)
compressionLevelNoCompression level 1-9 (optional, default 6)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it never says whether existing files at outputPath are overwritten, whether the operation is destructive to the input, or what permissions are needed. It also glosses over the relationship between the required outputPath and the optional extractDir, leaving a mutation tool's side effects undisclosed.

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?

Three terse sentences, front-loaded with the core verb and resource, with no filler. The telegraphic 'Input:/Output:' fragments are efficient, though 'Supports listing contents' never names the listOnly parameter it maps to.

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

Completeness3/5

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

For a seven-parameter mutating tool with no annotations and no output schema, the description covers formats and listing but leaves the extraction-vs-archive path semantics and the outputPath/extractDir overlap unexplained. It is adequate to call the tool, but not complete enough to predict its behavior confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all seven parameters are already documented, establishing the baseline of 3. The description's format lists add useful context but actually diverge from the schema enums (it omits zst output and tar.gz output, and omits zst input), so it adds only marginal, slightly inconsistent value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States specific verbs (compress/decompress) and the resource (archives), plus concrete format lists that let an agent distinguish this from convert_image/convert_audio-style siblings. It does not explicitly name a sibling to route away from, which keeps it below a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the format lists and the mention of listing contents, so an agent can infer this is the archive tool. There is no explicit when-to-use/when-not guidance versus batch_convert or get_supported_formats, and no prerequisites or error conditions are stated.

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