Skip to main content
Glama
Sign In
cmcp

cmcp

by DeveshB-1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Utilities/Deflate Compressed Response

utilities_deflate_compressed_response
Read-only

Returns a JSON echo of the request compressed with DEFLATE, letting you test client decompression when the Accept-Encoding header includes deflate.

Instructions

This endpoint returns the response using deflate compression algorithm. The uncompressed response is a JSON string containing the details of the request sent by the client. For this endpoint to work, one should request with Accept-encoding header containing deflate as part of its value. Postman supports gzip, deflate and SDCH decoding and automatically sends them as part of the request.

HTTP Compression allows the server to send responses in a compressed format, which is uncompressed by the client before processing. This reduces network bandwidth consumption at the cost of increase in CPU usage. To know more about this, refer the HTTP Compression wikipedia article.

(Postman request: Utilities/Deflate Compressed Response | GET https://postman-echo.com/deflate)

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": "utilities_deflate_compressed_response"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the operation as read-only, non-destructive, and open-world. The description adds useful behavioral detail beyond annotations: the response is compressed with deflate, the client must decompress it, and the header must request deflate for the endpoint to work.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the key deflate behavior, but it spends extra sentences on general HTTP compression education and includes Wikipedia links and a Postman request note. The core invocation guidance could be stated more compactly.

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?

For a zero-parameter GET echo endpoint with no output schema, the description is largely complete: it explains the required `Accept-encoding` header, the compression behavior, and that the decompressed body contains request details as JSON. It does not describe exact error behavior or response fields, but those are less critical for this simple tool.

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?

The tool has zero parameters, so there are no parameter semantics to document. The schema coverage is effectively 100% because the input object is empty, making the baseline score of 4 appropriate.

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?

The description states a specific action and resource: it returns the response using the deflate compression algorithm, and notes the uncompressed payload is a JSON string describing the client request. It is distinguishable from siblings by naming deflate, but it does not explicitly contrast itself with the gzip-compressed sibling.

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?

The description gives a concrete usage prerequisite: the request must include `Accept-encoding` with `deflate` in its value. It also mentions Postman supports gzip, deflate, and SDCH, which indirectly frames alternatives, but it does not explicitly say when to choose this endpoint over the gzip endpoint.

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