Tanod MCP server

imagepeek: make a favicon set from an image

image_favicon

Idempotent

Generate a complete favicon set from one image, including favicon.ico and PNG icons, HTML link snippet, and web-manifest entries.

Instructions

imagepeek: Generate a favicon set from an image. For plain sizes use image_thumbnail. Returns a favicon set from one image: favicon.ico (16, 32, 48 px), favicon-32x32.png, apple-touch-icon.png (180 px, flattened on apple_background, white by default), icon-192.png and icon-512.png, plus the HTML snippet and the web-manifest icons; a source under 512 px is upscaled, with a note. The images come back in images. 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/favicon-generator-api.html

Input Schema

TableJSON Schema

Name	Required	Description	Default
`fit`	No	Squaring a non-square image: cover (default, centre crop) or contain (padded with background).	cover
`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.
`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
`background`	No	contain padding (default transparent).
`auto_orient`	No	Apply the EXIF orientation first (default true).
`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.
`apple_background`	No	apple-touch-icon fill (default #ffffff).

Output Schema

TableJSON Schema

Name	Required	Description
`html`	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
`images`	No
`source`	No
`final_url`	No
`operation`	No
`source_url`	No
`total_bytes`	No
`manifest_icons`	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?

Annotations carry the safety profile (idempotent, non-destructive, open-world), and the description layers on a lot: exact artifacts produced, apple-touch flattening, upscaling behavior, accepted/refused formats, 40 MP refusal (not charged), EXIF/GPS/XMP/IPTC stripping, 413 limits, privacy (not logged), 24 h retention only with output=url, latency and pricing.

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 core purpose is front-loaded, followed by outputs, then limits/pricing. It is a dense single block with high information density, though the sheer volume of caveats makes it heavier than ideal for a quick scan.

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 a 7-parameter tool with an output schema, the description is more than complete: it covers accepted inputs, artifact list, size/time/cost constraints, and retention. Nothing an agent needs to call it correctly is missing.

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 baseline is 3, but the description adds real meaning: apple_background defaults to white and flattens the apple icon, and output=url is what triggers 24 h server retention versus inline base64. It stops short of tying fit/background to the squaring workflow explicitly.

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 ('Generate a favicon set from an image') and immediately distinguishes itself from the sibling image_thumbnail for plain size work. An agent can tell this is the specialized favicon-bundle tool without opening a 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?

Names an explicit alternative ('For plain sizes use image_thumbnail') with the condition that selects it, plus behavioral triggers like auto-upscaling under 512 px. It lacks guidance relative to the other image_* siblings (resize/convert), so not a full when/when-not map.

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

Deploy Server