Skip to main content
Glama

crop

Idempotent

Extracts a rectangular region from a PNG at specified x/y pixel coordinates and returns the resulting image.

Instructions

Crop a PNG to a rectangle in image pixels. Returns the image.

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": {
      "in": "<in>",
      "x": "<x>",
      "y": "<y>",
      "w": "<w>",
      "h": "<h>"
    },
    "name": "crop"
  }
}

Input Schema

NameRequiredDescriptionDefault
hYes
wYes
xYes
yYes
inYesPNG path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

The annotations already establish that the operation is idempotent, non-destructive, and closed-world. The description adds that the result is an image and that coordinates are in image pixels, but it does not clarify whether the returned image is a path, binary data, or how the original PNG is affected.

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 two short sentences and front-loads the core operation. There is no unnecessary wording, and the return behavior is stated immediately after the purpose.

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?

For a tool with five required parameters, 20% schema description coverage, no output schema, and mutation-adjacent annotations, the description is too sparse. It leaves important coordinate conventions and the exact return representation unspecified.

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?

Schema coverage is only 20%, with just the input path documented in the schema. The description says the rectangle is in image pixels, which gives general meaning to x, y, w, and h, but it does not define whether x/y is the top-left corner, how bounds are handled, or whether w/h are dimensions versus endpoints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: crop a PNG to a rectangle in image pixels. It is clear what operation the tool performs, though it does not explicitly distinguish the tool from nearby image operations such as mask or clip.

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives. An agent must infer that this tool is for PNG cropping rather than masking or other image transformations.

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