Skip to main content
Glama

zip_items

Compress one or more files or folders into a ZIP archive directly on the server, specifying source paths and a destination ZIP file.

Instructions

Compress one or more files/folders into a ZIP archive directly on the 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": {
      "sources": "<sources>",
      "dest_zip": "<dest_zip>"
    },
    "name": "zip_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourcesYesList of relative paths to compress.
dest_zipYesRelative path for the output ZIP file (e.g., backup.zip).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

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 carries the full behavioral burden, and it discloses only that work happens 'directly on the server'. It says nothing about overwrite behavior when dest_zip already exists, whether folder compression is recursive, permission requirements, or what happens on partial failure — all critical for a tool that creates files.

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 with no filler; the server-locality qualifier is the only embellishment and it earns its place. Nothing is buried or repeated.

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 two-parameter tool with complete schema documentation and no output schema, the definition is minimally viable but leaves the agent guessing about overwrite semantics and return behavior after a successful archive creation. A write tool without annotations or an output schema should say more about outcomes.

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 both parameters are already documented in structured form, making 3 the baseline. The description adds only that multiple items may be supplied and that paths are server-side relative paths; it adds no syntax, path resolution, or validation detail beyond the schema.

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 ('Compress') and resource ('ZIP archive') with clear input ('one or more files/folders'), so an agent can immediately tell this is the archive-creation tool. It does not explicitly name the complementary sibling (unzip_item), so differentiation is inferred from the description's own wording rather than stated.

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 versus when-not guidance, no prerequisites (e.g., that source paths must already exist on the server), and no mention of unzip_item as the inverse operation. The only usage signal is the implicit one carried by the purpose sentence itself.

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