Skip to main content
Glama

Cleanor

by app.cleanor
OverviewDiscussionsAdmin

Real storage savings of next-gen image formats

image_format_savings
Read-only

How much smaller WebP, AVIF or JPEG XL are than JPEG at matched perceptual quality, from Cleanor Labs’ controlled benchmark. Also reports the "HEIC conversion tax" (converting an iPhone HEIC to JPG/PNG makes it bigger). Use to justify a format choice when building a site or app.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoTarget format to compare against JPEG.avif
qualityNoweb = typical web quality (SSIM 0.95); high = near-lossless (SSIM 0.98).web

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatYes
sourceYes
qualityYes
all_formatsYes
percent_smaller_than_jpegYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "all_formats": {
+      "additionalProperties": false,
+      "properties": {
+        "avif": {
+          "type": "number"
+        },
+        "jxl": {
+          "type": "number"
+        },
+        "webp": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "avif",
+        "webp",
+        "jxl"
+      ],
+      "type": "object"
+    },
+    "format": {
+      "type": "string"
+    },
+    "percent_smaller_than_jpeg": {
+      "type": "number"
+    },
+    "quality": {
+      "type": "string"
+    },
+    "source": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "format",
+    "quality",
+    "percent_smaller_than_jpeg",
+    "all_formats",
+    "source"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With readOnlyHint=true, the description adds useful context beyond the annotation: the benchmark source ('Cleanor Labs’ controlled benchmark') and the additional HEIC conversion tax output. It does not contradict annotations and provides a clear behavioral picture without needing to describe side effects.

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?

Two sentences, front-loaded with the core value proposition, then the extra HEIC detail, and finally the use case. Every sentence earns its place; no filler or repetition of schema information.

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?

The tool has only 2 parameters with full schema descriptions, an output schema, and a clear description covering purpose, use case, and additional output. The agent has all necessary context to select and invoke the tool correctly.

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. The description adds meaning by explaining the 'matched perceptual quality' concept, which directly relates to the quality parameter. It also ties the format parameter to the comparison against JPEG, going beyond the schema's enum list.

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 specifies the tool's function: it quantifies storage savings of WebP, AVIF, and JPEG XL over JPEG at matched quality. It also mentions the HEIC conversion tax and explicitly states the intended use ('justify a format choice'), distinguishing it from sibling tools like optimize_image or placeholder_image.

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 an explicit use case: 'Use to justify a format choice when building a site or app.' It clearly indicates when to use the tool. It doesn't name alternatives or exclusion criteria, but the context is sufficient for an agent to decide between this and other image-related tools.

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

All Cleanor toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources