Loading ToolBench
Local-first MCP adapter and cloud-to-local bridge for QuokkaPix image and video workflows.
Quokkapix-MCP provides comprehensive tool definitions for image and video processing workflows with explicit schemas and descriptions. However, several quality issues prevent a higher score: (1) Parameter descriptions often lack format/constraint details (e.g., appUrl description doesn't explain allowed domains until reading payment-tools.mjs); (2) Output schemas are not documented, no description of what process_images or process_video return; (3) Error handling descriptions are absent; (4) Some tool names use '_with_settings' suffix which is slightly ambiguous compared to a clearer pattern; (5) Complex object parameters (recipe, settings) lack nested field documentation. Strengths: all 19 tools have descriptions (10-250 chars range), input parameters are typed with schema format, and tool names follow verb_noun pattern. The payment and validation tools are well-structured for read-only operations.
Get human-readable explanation of QuokkaPix x402 payment flow for agents.
Retrieve available payment options and product tiers from QuokkaPix for agent processing.
Retrieve a specific QuokkaPix recipe by id.
Retrieve a specific QA rule profile by id.
Retrieve a specific QuokkaPix video recipe by id.
Retrieve a specific video QA rule profile by id.
List all available official QuokkaPix recipes with metadata.
Output schemas not documented. Tools like process_images, process_video, and process_with_settings have no documented return schema. LLMs cannot plan downstream field extraction or understand what manifest structure to expect.
Complex object parameters lack nested field documentation. 'recipe' and 'settings' parameters are typed as 'object' with generic descriptions like 'Custom QuokkaPix recipe object' or 'Payload accepted by window.QuokkaPixAgent.applySettings'. LLMs cannot construct these objects without inline API knowledge.
appUrl parameter security guidance incomplete. Description mentions 'only quokkapix.com, localhost and 127.0.0.1 are accepted unless QUOKKAPIX_ALLOW_CUSTOM_APP_URL=1 is set' but this critical constraint appears only in the tool code comment, not in the parameter description visible to LLMs.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 63 | 2025-06-18+ | v2 |
List all available QA rule profiles for image result validation.
List all available official QuokkaPix video recipes.
List all available QA rule profiles for video result validation.
Process local images through QuokkaPix with specified recipe or settings, returning result manifest with output metadata.
Process local video through QuokkaPix with specified recipe or settings, returning result manifest.
Process local video through QuokkaPix with custom settings, returning result manifest.
Process local images through QuokkaPix with custom settings, returning result manifest with output metadata.
Validate a custom QuokkaPix recipe object before use.
Validate a QuokkaPix image result manifest against expected QA criteria.
Validate a custom QuokkaPix video recipe object before use.
Validate a QuokkaPix video result manifest against expected QA criteria.
Verify and validate an x402 unlock token for QuokkaPix processing tier access.
No error handling guidance in tool descriptions. Tools marked as WRITE operations (process_images, process_video) have no description of failure modes, retryability, or recovery guidance. LLMs cannot distinguish between transient (retry) and permanent (abort) failures.
Naming ambiguity: '_with_settings' suffix creates paired tools that differ only in input structure. 'process_images' vs 'process_with_settings' is less clear than 'process_images_with_recipe' vs 'process_images_with_settings'.
Parameter format constraints missing. 'unlockToken', 'recipeId', and 'settingsId' lack format descriptions (e.g., is recipeId 'shopify_product_pack' or a UUID?). 'timeoutMs' lacks min/max bounds.
File path parameters lack validation guidance. 'inputFiles', 'watermarkLogoFile', 'backgroundImageFile', 'outputDir' accept paths but don't document requirements (relative vs absolute, must exist vs created, character restrictions).