Skip to main content
Glama
Nizoka

zipnative-mcp

Inflate raw DEFLATE (bounded)

inflate_raw
Idempotent

Decompress raw DEFLATE streams with a mandatory output bound, returning base64 or file, and reporting consumed/trailing bytes.

Instructions

Decompress a raw DEFLATE (RFC 1951) stream — e.g. the payload from read_zip_entry mode:'raw' — with a MANDATORY maxOutput bound through zipnative's resumable inflater (constant memory, exact bytesConsumed, trailing bytes reported as leftover; ZIP_INFLATE_OUTPUT_OVERFLOW past the bound). method 'store' is a bounded pass-through; a numeric method id selects a registered codec (none beyond 0 / 8 in this server → ZIP_UNSUPPORTED_METHOD). Output base64 (≤ 50 MiB) or a sandbox file. Use it only for a raw payload or a bare deflate stream; to read an entry's content prefer read_zip_entry mode:'data'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodNo'deflate' (default, method 8), 'store' (method 0, bounded pass-through) or a numeric method id for a registered codec.deflate
maxOutputYesMandatory output bound in bytes: decompression stops with ZIP_INFLATE_OUTPUT_OVERFLOW beyond it (zip-bomb guard). Inline results are further capped at 52428800 bytes, file results at 4294967296.
dataBase64NoThe compressed stream as base64 (e.g. the payload from read_zip_entry mode:"raw"). Exclusive with sourcePath.
outputModeNo'base64' (default) returns the bytes inline as an embedded resource (≤ 50 MiB). 'file' writes them inside ZIPNATIVE_MCP_OUTPUT_DIR (never overwrites; ≤ 4 GiB, streamed) and returns a resource_link.base64
outputPathNoRelative path inside the sandbox (only when outputMode='file'); must end in a container extension (.zip recommended).
sourcePathNoRelative path of a file inside the sandbox holding the compressed stream (streamed). Exclusive with dataBase64.
allowTrailingNoAccept bytes after the end of the deflate stream silently (they are always reported as `leftover`).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes
summaryYesinflate_raw summary (the produced bytes are application/octet-stream, not an archive).
filePathNoSandboxed absolute path (file mode).
sizeBytesYes
diagnosticsYesNon-fatal conformance concerns the engine raised while parsing or writing (de-duplicated by code + entry, at most 200). Empty for a clean archive. Codes: ZIP_PREPENDED_DATA, ZIP_MULTIPLE_EOCD, ZIP_NAME_MISMATCH, ZIP_UNICODE_PATH_CONFLICT, ZIP_INVALID_UTF8_NAME, ZIP_DUPLICATE_NAME, ZIP_EXTRA_FIELD_MALFORMED, ZIP_ZIP64_EXTRA_IGNORED, ZIP_TIMESTAMP_NOT_PINNED, ZIP_NONDETERMINISTIC_CODEC, ZIP_DEAD_BYTES_RATIO.
diagnosticCountsNoNumber of diagnostics received per code (counts every occurrence, including de-duplicated ones).
diagnosticsTruncatedNoPresent (true) when more than 200 distinct diagnostics were dropped from `diagnostics`.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

The description discloses important runtime behavior: decompression stops past the bound with ZIP_INFLATE_OUTPUT_OVERFLOW, trailing bytes are reported as leftover, unsupported codecs raise ZIP_UNSUPPORTED_METHOD, and file outputs never overwrite. These details go beyond the annotations and accurately portray side effects and limits.

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 dense and information-rich but somewhat repetitive with repeated mentions of boundedness, output caps, and related error modes. It is still well structured and each clause contributes useful guidance, so it remains concise enough for practical use.

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

Completeness5/5

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

Given the tool's complexity, the description fully covers the required inputs, constraints, output mode choices, error conditions, and safe usage boundaries. It also provides enough context for an agent to decide when to use this tool versus read_zip_entry, making it complete in context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already covers all parameters, and the description adds meaningful semantics such as exclusivity between dataBase64 and sourcePath, the meaning of numeric method IDs, inline vs file output caps, and streamed file writes. This exceeds the baseline expected for fully covered schemas.

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 clearly identifies the operation as decompressing a raw DEFLATE (RFC 1951) stream, including the payload source such as read_zip_entry mode:'raw'. It is specific about the resource and action, and the title aligns with the described behavior.

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

Usage Guidelines5/5

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

The description explicitly states when to use the tool ('only for a raw payload or a bare deflate stream') and when to prefer an alternative ('to read an entry's content prefer read_zip_entry mode:"data"'). It also explains mandatory bounds, output modes, and codec selection, leaving little ambiguity.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nizoka/zipnative-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server