Skip to main content
Glama

image_edit

Edit images by resizing, cropping, rotating, flipping, converting format or quality, or applying grayscale to files or folders; originals are preserved.

Instructions

Resize (fit contain/cover/stretch; no upscale unless upscale), crop {x,y,width,height}, rotate, flip, grayscale, convert (quality); file or folder; never overwrites originals.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "image_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
fitNo
cropNo
flipNo
pathYes
widthNo
formatNo
heightNo
rotateNo90/180/270
suffixNo
out_dirNo
qualityNo
upscaleNo
grayscaleNo
overwriteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only supply destructiveHint=false, so the description carries most of the burden and does add real context: default no-upscale behavior, acceptance of a file or folder path, and preservation of originals. It stops short of explaining output naming (suffix/out_dir) or what happens when overwrite is set, which conflicts slightly with 'never overwrites originals'.

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?

A single dense sentence with operations front-loaded and constraints trailing after the semicolon. Telegraphic style is efficient, though the parenthetical shorthand ('quality', 'convert') is terse enough to be slightly ambiguous.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 14-parameter mutation tool with near-zero schema documentation and no output schema, the description covers the core operations but omits output destination/naming and overwrite semantics, leaving meaningful gaps an agent would need to guess at.

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 only 7% across 14 parameters, so the description must compensate. It clarifies fit modes, crop shape, rotate values, flip axis, grayscale, quality, and upscale, but leaves format, width/height, suffix, out_dir, and overwrite unexplained.

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?

Names specific operations (resize, crop, rotate, flip, grayscale, convert) on a specific resource (images), and states scope: 'file or folder'. An agent can distinguish this from image_compare or media_info without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Gives useful behavioral rules ('no upscale unless upscale', 'never overwrites originals') that imply when the tool is safe to use, but never states when to prefer it over siblings or what preconditions apply. Usage is implied rather than directed.

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