Tanod MCP server

imagepeek: compress an image (optionally to a byte budget)

image_compress

Idempotent

Compress an image to a smaller JPEG, WebP, AVIF or PNG, with metadata stripped. Set a quality or max_bytes target to get the highest quality that fits.

Instructions

imagepeek: Compress an image, optionally to a byte budget. To change the format only use image_convert. Returns a smaller JPEG, WebP, AVIF or PNG with metadata stripped: at quality, or with max_bytes the highest quality that fits (target_met false when none does); PNG can be quantised to colors. It never returns a larger file (the original comes back with returned_original: true). Reads PNG, JPEG, WebP, GIF, TIFF, BMP, ICO and AVIF; other formats and images over 40 megapixels are refused (not charged). Output: base64 data_base64, without EXIF, GPS, XMP or IPTC; over 15 MB or 50 megapixels is a 413 (not charged). Images are not logged; a result is kept only with output "url" (24 h). Typically 0.5-2 s. Price: USD 0.003. Free: 3 imagepeek calls per IP per UTC day. Docs: https://tanod.dev/learn/image-compress-api.html

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	No	Public http(s) URL of the image (at most 10 MB; private, internal and IP-literal hosts are refused); or use image_base64.
`colors`	No	png: quantise to this many colours.
`format`	No	Output format: jpeg, png, webp or avif (default: the input's).
`output`	No	base64 (default): the file comes back inline as base64. url: the file is stored for 24 hours and the reply carries a download link (url, expires_at, bytes, content_type, sha256) instead of the base64, which keeps the file out of your context window.	base64
`quality`	No	Target (or, with max_bytes, highest) quality.
`keep_icc`	No	Keep the ICC colour profile (default true).
`lossless`	No	webp only: lossless encoding (default false).
`max_bytes`	No	Size target: the highest quality that fits.
`auto_orient`	No	Apply the EXIF orientation first (default true).
`progressive`	No	jpeg only: progressive encoding (default false).
`image_base64`	No	The image as standard or url-safe base64 (at most 10 MB decoded; a data:image/...;base64, prefix is fine); or use url.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	No
`bytes`	No
`error`	No	Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
`input`	No
`notes`	No
`width`	No
`format`	No
`height`	No
`sha256`	No
`source`	No
`encodes`	No
`final_url`	No
`operation`	No
`expires_at`	No
`source_url`	No
`target_met`	No
`after_bytes`	No
`data_base64`	No
`saved_bytes`	No
`saved_ratio`	No
`before_bytes`	No
`content_type`	No
`quality_used`	No
`returned_original`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Far exceeds the annotations: metadata is stripped (EXIF/GPS/XMP/IPTC), the result is never larger and returned_original flags the fallback, target_met reports budget failure, unsupported formats and >40 MP inputs are refused without charge, >15 MB/50 MP yields a 413 without charge, images are not logged and results persist only with output='url' (24 h), plus latency and price. All of this is behavioral detail the readOnly/idempotent/destructive hints cannot convey.

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?

Dense but front-loaded: purpose and sibling routing come first, then behavior, then limits/pricing. Slightly crammed into one block with pricing, free tier and a docs URL stacked at the end, but essentially every clause carries information an agent needs.

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?

For an 11-parameter, no-required-parameter transformation tool with an output schema and annotations, the description covers inputs, output shape (base64 data_base64), failure modes, retention, cost and latency. Nothing needed to call it correctly is missing; return-value detail is legitimately delegated to the output schema.

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 description coverage is already 100%, so the baseline is 3, but the description adds interaction semantics the schema does not: quality is a target that becomes 'highest that fits' when max_bytes is supplied, and target_met signals when no fit was found. It also ties colors specifically to PNG quantisation, reinforcing the schema wording.

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?

States a specific verb and resource ('Compress an image') and immediately scopes it ('optionally to a byte budget'), then explicitly names the sibling it is not ('To change the format only use image_convert'). An agent can distinguish it from image_resize, image_thumbnail and image_convert without opening any schema.

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?

Gives clear routing context: change format only -> image_convert, and implies this tool for size reduction (quality / max_bytes / colors). However it never contrasts with the other compression-adjacent siblings (image_thumbnail, image_strip_metadata, image_resize), so there are no explicit when-not cases beyond the format-only one.

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

Deploy Server