Skip to main content
Glama

unzip_item

Extract a ZIP archive directly on a cPanel server to a chosen destination directory, avoiding manual file uploads or SSH.

Instructions

Extract a ZIP archive directly on the cPanel server.

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": {
      "zip_path": "<zip_path>"
    },
    "name": "unzip_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
dest_dirNoRelative destination directory for extraction (leave empty for root).
zip_pathYesRelative path to the ZIP archive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/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 burden of behavioral disclosure. Beyond noting that extraction happens server-side (no download step), it says nothing about whether existing files are overwritten, what happens on a missing destination directory, size or permission limits, or whether the archive is removed afterward — significant gaps for a filesystem-mutating tool.

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?

A single front-loaded sentence with no wasted words; the operation and execution locus come first. It is efficiently written, though the terseness leaves behavioral questions unanswered rather than being genuinely complete.

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 mutating filesystem operation with zero annotations and no output schema, the definition is too thin: it omits overwrite semantics, error conditions, and any note on what the call returns or where files land relative to the account root. The schema is fully documented, but the behavioral side is not covered.

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 description coverage is 100%, with both zip_path and dest_dir documented including the default and 'leave empty for root' semantics. The description adds no further meaning beyond the schema, so the baseline 3 applies.

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 a specific verb ('Extract') and resource ('a ZIP archive') plus the execution context ('directly on the cPanel server'), which implicitly contrasts with the zip_items sibling that creates archives. It stops short of explicitly naming the complementary tool, but an agent can identify the operation without opening the schema.

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?

There is no guidance on when to use this versus alternatives, no prerequisites (e.g. whether dest_dir must already exist, or whether the archive must reside within the account's home), and no mention of overwrite behavior when files already exist. The agent is left to infer all preconditions.

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