Skip to main content
Glama

Process local images with direct QuokkaPix settings

process_with_settings

Process local image files with direct QuokkaPix agent settings for custom resize, crop, convert, compress, and scenario workflows.

Instructions

Process local image files with a direct window.QuokkaPixAgent.applySettings payload instead of an official recipe. Use this for custom resize/crop/convert/compress/background/watermark/effects/rename/PDF/favicon/scenario workflows. For multi-step scenarios, prefer settings.steps as [{ tool, settings }]. The adapter downloads the output, writes quokkapix-result.json and returns QA results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appUrlNoOptional QuokkaPix app URL. Defaults to https://quokkapix.com/#agent=1. For safety, only quokkapix.com, localhost and 127.0.0.1 are accepted unless QUOKKAPIX_ALLOW_CUSTOM_APP_URL=1 is set.
headlessNoRun Chromium headless. Defaults to true unless debugging.
maxFilesNoMaximum allowed input files for this direct settings run. Defaults to the selected files count.
settingsYesPayload accepted by window.QuokkaPixAgent.applySettings. Extra editor-specific keys are allowed.
outputDirYesLocal directory where the adapter writes the downloaded output and quokkapix-result.json.
timeoutMsNoMaximum processing timeout in milliseconds.
inputFilesYesLocal source image files to upload through the browser file input.
settingsIdNoOptional id/name for this generated settings workflow, used in returned metadata and QA profile.
unlockTokenNoOptional x402 unlock token for paid agent batch/scenario runs above 5 files.
expectedResultQaNoOptional QA contract used to validate quokkapix-result.json after processing.
watermarkLogoFileNoOptional local logo/image file for logo watermark settings.
backgroundImageFileNoOptional local image file for background replacement settings.
Behavior4/5

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

With no annotations, the description discloses key behaviors: it downloads output, writes quokkapix-result.json, uses Chromium with headless default, applies URL safety restrictions, and supports unlock tokens for paid runs. This is robust for a processing tool.

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?

The description is concise (5 sentences), front-loads the main purpose, and each sentence adds essential information without redundancy.

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 complex tool with 12 parameters and no output schema, the description covers purpose, usage guidance, safety, and workflow. It could detail the return structure, but the expectedResultQa parameter and mention of QA results partially compensate.

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% with good parameter descriptions. The description adds value by explaining the overall flow and noting that extra editor-specific keys are allowed in settings, which schema cannot convey.

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 states the tool processes local image files using a direct QuokkaPix settings payload, distinguishing it from recipe-based tools like process_images. The title 'direct QuokkaPix settings' reinforces the unique value.

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 explicitly recommends this tool for custom workflows and mentions preferring settings.steps for multi-step scenarios. It differentiates from official recipes, providing clear context, though it does not explicitly state when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/quokkapix/quokkapix-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server