Skip to main content
Glama

Simpler.Asia

image.adjust

Apply 1..10 adjustments to a photo in order, with the editor's own kernels: a one-op stack returns the same pixels as that tool in the editor. ops is a list of {op, params}; each op takes only its own params keys, and a key left out takes that op's default: brightness_contrast (brightness, contrast), exposure (stops), temperature_tint (temperature, tint), vibrance_saturation (vibrance, saturation), curves (rgb, red, green, blue), levels (in_black, in_white, levels_gamma, out_black, out_white), hsl_per_range (range, hue, saturation, luminance), sharpen (amount, radius, shadow_protect, highlight_protect), blur (radius), denoise (luminance_strength, chrominance_strength, radius), vignette (amount, midpoint, feather), grain (amount), black_and_white (red_weight, green_weight, blue_weight, tint_color), auto_tone (aggressive). output_format is png (the default, free), jpeg or webp ($0.0005 for the one Images encode, charged only when the result is delivered). Free for png output, $0.0005 for jpeg or webp: runs on the platform's own deterministic kernel, so the same input and arguments always return the same pixels. Takes PNG, JPEG, WebP, GIF or HEIC. Returns JSON {images:[{url, asset_key, download_url?, width, height}], price, next} plus a preview; images are stored in this workspace. Refuses: SIMPLER_MEDIA_INPUT_MISSING (pass the url or the asset_key), SIMPLER_MEDIA_FOREIGN_KEY (use this workspace's asset_key), SIMPLER_MEDIA_URL_REFUSED (use https, data:image or an asset_key), SIMPLER_MEDIA_PIN_TOO_LARGE (under 20MB), VALIDATION_ERROR with reason SIMPLER_EDIT_TOOL_ARGS_INVALID for an unknown op, a key the op does not take, a value outside the op's range, levels with in_white not above in_black, or an output_format outside png, jpeg and webp, SIMPLER_EDIT_SERVER_PIXELS_NEEDS_PNG (the file is not an image: send a PNG, JPEG, WebP, GIF or HEIC), SIMPLER_EDIT_SERVER_PIXELS_TOO_LARGE (at most 4,194,304 pixels: run image.convert with width and height 2048 first), SIMPLER_IMAGES_BINDING_ABSENT (this deployment has no Images binding yet, owner step O-2: send a standard PNG), SIMPLER_IMAGES_QUOTA_EXCEEDED or SIMPLER_IMAGES_LEGACY_SUBSCRIPTION (an owner account step: send a standard PNG meanwhile), SIMPLER_IMAGES_INPUT_UNREADABLE (send a PNG, JPEG, WebP, GIF or HEIC), SIMPLER_IMAGES_INPUT_TOO_LARGE (under 20,000,000 bytes and 100 megapixels), SIMPLER_IMAGES_TRANSFORM_FAILED (retry, or send a standard PNG); nothing is charged on any of them, and INSUFFICIENT_CREDITS or PAYMENT_REQUIRED only when the workspace is already overdrawn or past its spend cap (add credits or raise the cap). NEXT: pass images[0].asset_key as image_asset_key to the next image.* tool, or open download_url when the result carries one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opsYesAdjustments applied in order, 1..10. Each op takes only its own params keys: brightness_contrast (brightness, contrast), exposure (stops), temperature_tint (temperature, tint), vibrance_saturation (vibrance, saturation), curves (rgb, red, green, blue), levels (in_black, in_white, levels_gamma, out_black, out_white), hsl_per_range (range, hue, saturation, luminance), sharpen (amount, radius, shadow_protect, highlight_protect), blur (radius), denoise (luminance_strength, chrominance_strength, radius), vignette (amount, midpoint, feather), grain (amount), black_and_white (red_weight, green_weight, blue_weight, tint_color), auto_tone (aggressive).
image_urlNoPhoto to adjust: a public https URL, a data:image/...;base64 URL, or the url/url_path of an earlier image result (max 20MB; PNG, JPEG, WebP or GIF; SVG is refused). Pass this or the matching *_asset_key, not both.
request_refNoOptional idempotency key (1-64 chars: letters, digits, . _ : -). Retrying with the same request_ref and the same arguments within 24 hours returns the first result at $0 with replayed: true; the same request_ref with different arguments is refused (SIMPLER_IMAGE_REQUEST_REF_CONFLICT), and so is a retry whose first result was deleted since (SIMPLER_IMAGE_REQUEST_REF_RESULT_DELETED): send a new request_ref to run it again.
output_formatNoResult encoding: png (the default, free), jpeg or webp ($0.0005, one Images encode at quality 85; a JPEG has no transparency, so transparent pixels come out white).
preview_formatNoPreview block after the JSON, at most 384px on the long edge and never charged: png, jpeg or none. Left out, a PNG result gets a png preview and a JPEG or WebP result a jpeg one. A result with no preview says why in preview_unavailable.
image_asset_keyNoPhoto to adjust, as the asset_key of an earlier image result for this workspace (edit-projects/<tenant>/... or images/<tenant>/...). A key from another workspace is refused (SIMPLER_MEDIA_FOREIGN_KEY).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations carry only readOnlyHint=false, so the description carries the disclosure burden and does so richly: cost model (free PNG, $0.0005 for jpeg/webp encode), determinism, accepted input formats, pixel/size limits, and a comprehensive enumerated refusal taxonomy with remediation for each. It also discloses that nothing is charged on refusals except overdrawn/spend-cap cases.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, ops and pricing, which is good, but the refusal-code enumeration is a dense, run-on block that dominates the text and makes it hard to scan. Much of it earns its place operationally, yet the whole is overlong for what an agent needs to select and invoke the tool.

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?

No output schema exists, and the description fully specifies the return shape ({images:[{url, asset_key, download_url?, width, height}], price, next} plus preview), storage location, and the chaining step via asset_key. Given the tool's complexity, nothing material is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description's per-op param mapping largely restates the ops schema description. It does add the rule that each op takes only its own keys and omitted keys fall to defaults, and clarifies output_format pricing, but most parameter detail is already structured.

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 (apply ordered adjustments) and resource (a photo), plus distinguishing scope: 1..10 ops in order, using the editor's own kernels. An agent can tell this apart from image.convert or image.generate because the description anchors it to the editor's adjustment stack and the ops list.

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?

Gives clear invocation context: one-op stack matches that editor tool, ops applied in order, 1..10 max, and identical input/args are deterministic. It also routes failure cases to alternatives (run image.convert with 2048 width/height when pixels exceed the cap) and tells the agent to chain via asset_key to the next image.* tool. It stops short of an explicit 'use X instead of this tool' comparison across all siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources