Skip to main content
Glama
webcafeina

Apolo

by webcafeina
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

empezar_lote

Starts background batch conversion of folders or many images, including subfolders, without overwriting files, and immediately returns an ID for later status checks.

Instructions

Converts folders or many images in the background, subfolders included, without overwriting anything, and comes back right away with an id. By default, WebP at score 80, in a folder next to the input one (photos-webp, or photos-apolo with several formats); with loose images, in a subfolder next to them (webp/, apolo/). One at a time. Afterwards, ver_lote. Example: {"entradas": ["~/Photos/trip"], "formatos": ["webp", "avif"], "mas_ligero": true}

Input Schema

NameRequiredDescriptionDefault
altoNoMaximum height, in pixels: scales down if larger and never enlarges (with ancho alone, proportional).
anchoNoMaximum width, in pixels: scales down if larger and never enlarges (with alto alone, proportional).
medirNoMeasure the score of each file (takes longer).
ordenNoOptions of the official tool (only with one format).
paletaNoReduce the palette to this number of colors (2 to 256), with dithering.
presetNoA saved preset, the base for everything.
salidaNoOutput folder. By default, next to the input one with -webp, -apolo…; with loose images, a webp/, apolo/… subfolder next to them.
calidadNoFixed quality from 0 to 100. Not together with nota_objetivo.
entradasYesFolders or images, absolute paths (~ is accepted).
formatosNoOutput formats (one or several). By default, the preset's or webp.
enderezarNoAuto-rotate each photo according to its EXIF orientation if it needs it. Yes by default.
lado_mayorNoMaximum longest side, in pixels: the width if landscape, the height if portrait; never enlarges. Not together with ancho, alto or porcentaje.
mas_ligeroNoWith several formats: keep only the lightest one of each image.
porcentajeNoReduce to this percentage (50 = half the width and height). From above 0 to 100. Not together with ancho, alto or lado_mayor.
sin_perdidaNoLossless (WebP, AVIF, JPEG XL). PNG and QOI always are.
nota_objetivoNoSearch, image by image, for the quality that gives this score. 80 by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false; the description adds real context on top: asynchronous fire-and-return with an id, never overwriting existing files, default output naming, and serial execution. It doesn't cover failure handling or how cancellation interacts with cancelar_lote, so it's strong rather than complete.

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?

Front-loaded with the core action and return semantics, and every clause carries information (defaults, output location, sequencing). The long parenthetical sentence about default folders is dense and slightly run-on, which keeps it from a 5.

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 16-parameter asynchronous mutation with no output schema, the description covers the return contract (an id) and the next tool to call, plus the defaults an agent needs to omit parameters safely. Only error/progress behaviour is left unaddressed.

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, but the description earns more by adding default behaviour not in the schema (WebP at score 80, photos-webp / photos-apolo folder naming) and a concrete example combining entradas, formatos and mas_ligero.

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: converts folders or many images in the background, subfolders included, returning an id immediately. That cleanly separates it from optimizar_imagen (single image) and ver_lote (polling the result).

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 names the follow-up step explicitly ("Afterwards, ver_lote") and says "one at a time", which tells the agent batches are serialized. It doesn't say when to prefer optimizar_imagen over a one-item batch, but the batch/single split is strongly implied.

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