Skip to main content
Glama
Sign In
ellmos-clatcher-mcp

ellmos-clatcher-mcp

Official
by ellmos-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

archive

Create, extract, or list ZIP archives. Compress files into ZIP format or decompress existing archives with preview and overwrite controls.

Instructions

Create, extract, or list ZIP archives.

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": {
      "action": "<action>",
      "archive_path": "<archive_path>"
    },
    "name": "archive"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesOperation
dry_runNoPreview create/extract without changing files
overwriteNoAllow extraction to overwrite existing files
extract_toNoExtraction directory (for extract)
archive_pathYesPath to the ZIP file
source_pathsNoFiles/directories to add (for create)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.16
    • addedInput schema / properties / dry_run
      Added value: +{
+  "default": true,
+  "description": "Preview create/extract without changing files",
+  "type": "boolean"
+}
    • addedInput schema / properties / overwrite
      Added value: +{
+  "default": false,
+  "description": "Allow extraction to overwrite existing files",
+  "type": "boolean"
+}
  2. First observedv1.0.5

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must carry the burden of behavioral disclosure, but it only restates the action enum from the schema. It does not mention the dry_run default, overwrite safety, the need for source_paths during create, or what 'list' returns. The drug is minimal and adds nothing beyond the schema's existing param descriptions.

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 description is a single, front-loaded sentence with no redundancy. It is appropriately short, but it sacrifices enough detail that the tool feels under-specified for its complexity.

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?

Given that there is no output schema and no annotations, the description should at least clarify action-dependent parameters, the meaning of dry_run, and the expected behavior of list. It provides none of this, leaving significant ambiguity for an agent trying to invoke the tool correctly.

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%, so the schema already documents all parameters and their roles. The description adds no additional parameter-level meaning, so the baseline score of 3 is appropriate.

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?

The description names specific verbs (create, extract, list) and a specific resource (ZIP archives), making the tool's purpose immediately clear. It also distinguishes itself from the sibling tools, which are all focused on fixing, converting, or checking files rather than archiving.

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 explicit guidance about when to use this tool versus an alternative, no conditions, and no exclusions. The intended use is only implied by the operation names and the schema, which is not enough for an agent to confidently decide between this and other file-related utilities.

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