Tanod MCP Server (Deprecated)

by dev.tanod

Overview Discussions Admin

This connector has been deprecated

The correct URL is https://tanod.dev/mcp and NOT https://tanod.dev/mcp/ (CORRECT: NO TRAILING SLASH)

Correct Glama listing: https://glama.ai/mcp/connectors/dev.tanod/tanod

WRONG Glama listing: https://glama.ai/mcp/connectors/dev.tanod/tanod-mcp-server/

imagepeek: crop an image

image_crop

Idempotent

imagepeek: Crop an image to a box or an aspect ratio. To scale instead use image_resize. Returns the image cropped to a box (left, top, width, height; out of bounds is a 422 crop_out_of_bounds) or to an aspect ratio such as 16:9 placed by gravity (center or a side or corner); the reply carries the applied box. 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.002. Free: 3 imagepeek calls per IP per UTC day. Docs: https://tanod.dev/learn/image-crop-api.html

Input Schema

Name	Required	Description	Default
`top`	No	Box mode: top edge in pixels.
`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.
`left`	No	Box mode: left edge in pixels (give left, top, width and height together, or aspect).
`width`	No	Box mode: crop width in pixels (1-32768).
`aspect`	No	Instead of a box, e.g. 16:9, with gravity.
`format`	No	Output format (default: the input's; ICO in, PNG out).
`height`	No	Box mode: crop height in pixels (1-32768).
`output`	No	base64 (default): inline. url: stored for 24 hours; link, metadata.	base64
`gravity`	No	Aspect mode: the part to keep: center (default), north, south, east, west, northwest, northeast, southwest or southeast.	center
`quality`	No	Encoder quality 1-100 (lossy formats).
`auto_orient`	No	Apply the EXIF orientation first.
`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

Name	Required	Description
`box`	No
`url`	No	Public link.
`bytes`	No	Bytes.
`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	SHA-256.
`source`	No
`final_url`	No
`operation`	No
`expires_at`	No	UTC expiry.
`source_url`	No
`data_base64`	No
`content_type`	No	MIME type.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 28, 2026

changedInput schema / properties / output / description

Previous value: -"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."New value: +"base64 (default): inline. url: stored for 24 hours; link, metadata."

addedOutput schema / properties / bytes / description
```
Added value: +"Bytes."
```
addedOutput schema / properties / content_type / description
```
Added value: +"MIME type."
```
addedOutput schema / properties / expires_at / description
```
Added value: +"UTC expiry."
```
addedOutput schema / properties / sha256 / description
```
Added value: +"SHA-256."
```
addedOutput schema / properties / url / description
```
Added value: +"Public link."
```

First observedOct 22, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnly=false, idempotent, non-destructive) by disclosing error semantics (422 crop_out_of_bounds, 413 for oversize), format support and 40 MP refusal, metadata stripping (EXIF/GPS/XMP/IPTC), privacy (images not logged, URLs kept 24h), latency and pricing. This is exactly the mutation-side context annotations 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?

Purpose and the image_resize alternative are front-loaded, then constraints follow. It is dense and long, but nearly every clause carries operational value; minor cost from cramming pricing, limits and docs into one block.

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 12-parameter image mutation tool with an output schema, the description covers modes, limits, errors, privacy and storage lifetime. An agent has everything needed to select and invoke it correctly; return-format detail is correctly deferred 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 coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema: which parameters group together for box vs aspect mode, that the reply carries the applied `box`, and the out-of-bounds consequence. It stops short of explaining `quality`/`auto_orient` interplay, so not a 5.

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 (crop) and resource (image) with the two operating modes (box or aspect ratio). It explicitly names the distinguishing sibling: 'To scale instead use image_resize', letting an agent separate it from image_resize and image_thumbnail 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 Guidelines5/5

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

Explicitly routes the scale case to image_resize, and describes when each mode applies: box (`left`, `top`, `width`, `height`) versus aspect with `gravity`. The alternative-tool condition is stated outright rather than left to inference.

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

All Tanod MCP Server (Deprecated) tools Inspect

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

Need Help?