Skip to main content
Glama

archive

List, extract, or create zip, tar, tgz, and gz files with path-escape prevention, link blocking, size limits, and CRC checks.

Instructions

List, extract, create zip/tar/tgz/gz safely (no path escape, no links, size limit, CRC check).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "archive"
  }
}

Input Schema

NameRequiredDescriptionDefault
opNo
cwdNo
pathNo
filesNo
formatNo
inputsNocreate
max_mbNo
out_dirNo
overwriteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3/5.0
Behavior3/5

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

Annotations only declare destructiveHint=false, so the description usefully adds the safety envelope: no path escape, no symlinks/hardlinks, size limit, CRC verification. That is real context beyond the annotation. However, it omits the overwrite behavior (a write op with an overwrite flag should say what happens to existing files) and what happens when a safety check fails.

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?

A single front-loaded sentence that names the actions, the formats, and the safety guarantees with zero filler. Every clause earns its place.

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

Completeness2/5

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

For a 9-parameter tool with no output schema, the description should explain at minimum the list output shape, overwrite semantics, and out_dir vs cwd relationship. None of that is present, leaving an agent to guess on the parameters that matter most for extraction and creation.

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

Parameters2/5

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

Schema description coverage is only 11% (only 'inputs' is annotated), so the description must compensate and largely does not. It implicitly covers op, format (by naming the four formats), and max_mb ('size limit'), but cwd, path, files, out_dir, and overwrite get no meaning at all.

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 three specific verbs (list, extract, create) against a specific resource set (zip/tar/tgz/gz). An agent immediately knows this is archive manipulation. It does not differentiate itself from the sibling tool named 'extract', which is the one real ambiguity.

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

Usage Guidelines2/5

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

No statement of when to use this versus the sibling 'extract', nor when to prefer one op over another, nor any prerequisites. The op enum in the schema carries all the routing information; the description itself offers none.

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