Skip to main content
Glama
epi13
by epi13

crop_image

Crop an image to a specified width, height, and offset. Directly applies the crop to the image in local GIMP.

Instructions

Crop an image to the supplied rectangle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthYes
heightYes
image_idYes
offset_xNo
offset_yNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the crop modifies the image in place, creates a new image, or how offsets affect the result. This leaves the operation's safety and side effects unclear.

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 a single concise sentence with no superfluous words. It is appropriately short, though under-specified in other dimensions.

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

Completeness2/5

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

Given 5 parameters and no annotations or schema descriptions, the description is inadequate for correct usage. It does not explain how the rectangle is defined or whether the operation targets the image identified by image_id.

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

Parameters2/5

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

The schema has 0% description coverage, and the description only vaguely refers to a 'supplied rectangle' without explaining the roles of width, height, offset_x, and offset_y. The agent must infer the parameter semantics from names alone.

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 uses a specific verb 'crop' and resource 'image', and the phrase 'supplied rectangle' indicates the operation scope. It clearly distinguishes from sibling tools like resize_image or rotate_image.

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

Usage Guidelines2/5

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

No guidance is provided on when to use crop_image versus alternatives like resize_image or select_rectangle. The description does not mention any prerequisites or exclusions.

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/epi13/gimp-local-mcp'

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