MCPDactyl

Decompress an archive

files_decompress

Extract an archive file into a specified root directory, optionally targeting a saved panel, to make compressed server files accessible.

Instructions

Extract an archive file under a root directory.

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": {
      "server": "<server>",
      "file": "<file>"
    },
    "name": "files_decompress"
  }
}

Input Schema

Name	Required	Description
`file`	Yes
`root`	No
`panel`	No	Name of a saved panel. Omit to use the active or default panel.
`server`	Yes
`baseUrl`	No	Inline panel URL override, e.g. https://panel.example.com. Not persisted.
`clientKey`	No	Inline client API key (ptlc_…) override. Not persisted.
`applicationKey`	No	Inline application API key (ptla_…) override. Not persisted.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 25, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full disclosure burden, yet it says nothing about overwrite behavior, supported archive formats, extraction target naming, or required permissions. Only the vague "under a root directory" hints at path containment, leaving the destructive potential of a filesystem write unexplained.

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 zero filler. The brevity costs specification rather than clarity, so it is efficient but under-informative rather than padded.

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?

A 7-parameter, filesystem-mutating tool with no annotations and no output schema; the description should at minimum cover overwrite behavior, source-vs-target path semantics, and format support. One sentence cannot carry that, so the definition is incomplete for the tool's complexity.

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 57%: 'file', 'server' and 'root' have no schema descriptions. The description loosely maps 'file' to the archive and 'root' to a base directory, but adds no format, path-resolution, or server-vs-panel semantics beyond that. Baseline 3 for moderate coverage is appropriate.

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 ("an archive file") plus a scoping note ("under a root directory"). Clear enough to distinguish from files_compress, but it never names the inverse sibling or explains the root scoping.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as files_compress or files_pull. An agent must infer from the name that this is the inverse of compression and that a target root must exist.

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

Deploy Server