Skip to main content
Glama
mcp-airlock

mcp-airlock

by sigma5667

GZip File as Resource Tool

gzip-file-as-resource
Idempotent

Compresses a single file with gzip and returns it as a resource or a downloadable resource link, so clients can fetch the compressed data in a later request.

Instructions

Compresses a single file using gzip compression. Depending upon the selected output type, returns either the compressed data as a gzipped resource or a resource link, allowing it to be downloaded in a subsequent request: during the current session for a 2025-era client, or for ten minutes at a minted URI on protocol version 2026-07-28.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gzip-file-as-resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNoURL or data URI of the file content to compresshttps://raw.githubusercontent.com/modelcontextprotocol/servers/refs/heads/main/README.md
nameNoName of the output file (at most 255 characters)README.md.gz
outputTypeNoHow the resulting gzipped file should be returned. 'resourceLink' returns a link to a resource that can be read later, 'resource' returns a full resource object.resourceLink

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior beyond that: the returned link's lifetime is session-scoped for a 2025-era client and ten minutes for a minted URI on protocol version 2026-07-28, which materially affects how the agent must consume the result.

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 sentences, front-loaded with the core action, with no filler. The trailing protocol-version clause is dense and slightly awkward to parse but carries real information, so it earns its place rather than being wasteful.

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?

With no output schema, the description must describe the return, and it does so for both output types including link lifetime. Missing only edge-case behavior (unreachable source URL, compression failures, size limits) and the implicit network fetch of the 'data' URI, which the openWorldHint annotation partly signals.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description earns an increment by stating the downstream consequence of the outputType choice and the differing validity windows of each return form — information not present in the enum descriptions. Data/name semantics are left entirely to the schema, which is acceptable given full coverage.

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+resource: 'Compresses a single file using gzip compression.' An agent immediately knows the operation and its scope (single file), and none of the siblings listed do anything similar, so no disambiguation is needed.

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

Usage Guidelines4/5

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

It gives clear context for the key decision — choosing between 'resourceLink' and 'resource' returns — by explaining that a link can be downloaded in a subsequent request. It stops short of explicit when-to-use/when-not guidance (e.g., 'prefer resourceLink for large files' or failure conditions), so it is clear but not complete routing guidance.

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