Skip to main content
Glama

zip_text_files

Read-onlyIdempotent

Create an exact ZIP of caller-supplied named UTF-8 texts. Preserves bytes and nested safe paths; rejects traversal, duplicate/colliding names and excessive data. No external files or fetches. Official documentation: https://creora.darwin.so/providers/files/docs

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": {
      "files": "<files>"
    },
    "name": "zip_text_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYes

Output Schema

NameRequiredDescriptionDefault
artifactsYes
sheetNamesYes
sourceSha256Yes
externalWritesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the description adds genuine extra context: exact byte preservation, safe nested paths, rejection of traversal, duplicate/colliding names and excessive data, and no network fetching. The main gap is that it doesn't say what the failure response looks like when an entry is rejected.

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?

Two dense sentences with the core purpose front-loaded and the constraints following in a compact list. The trailing documentation URL is the only element that doesn't directly help an agent decide or call, but it is short enough not to hurt.

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

Completeness4/5

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

An output schema exists, so return-value explanation is correctly omitted, and the description covers determinism, path safety and input validation for a single-parameter tool. The remaining hole is the undocumented per-field constraints, which an agent would only discover by reading the raw schema.

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 0% — neither the top-level 'files' array nor its 'name'/'text' item fields are documented in the schema. The description partially compensates by establishing that each entry is a named UTF-8 text and that names may contain safe nested paths, but it never explains the per-field limits (32 items, 160-char name, 128KB text).

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 opens with a specific verb and resource: 'Create an exact ZIP of caller-supplied named UTF-8 texts.' This is immediately distinguishable from the sibling converters (csv_to_xlsx, markdown_to_pdf, etc.), which all transform formats rather than packaging inline text into an archive.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: 'caller-supplied' and 'No external files or fetches' tell the agent that only inline text can be zipped, and the rejection list flags inputs that will fail. However, there is no explicit when-to-use versus alternatives guidance or statement of prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources