Skip to main content
Glama

Image Crop API - crop to ratio, box or trim borders

image_crop
Read-onlyIdempotent

Crop images to a ratio (1:1, 4:5, 16:9, 9:16, 3:2), to a pixel box, or trim uniform borders automatically. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.002 per call via x402 at https://radarbg.com/x402/image-crop.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mode": "ratio",
      "ratio": "1:1",
      "fileName": "sample.png",
      "fileContent": "iVBORw0KGgoAAAANSUhEUgAAAHgAAABQCAIAAABd+SbeAAAA6klEQVR4nO3cQQ2DABAAwdKgg1cFVQIykIOEyqiIisFDKdsQZv6XXDb3vmFa3jeOd//3AlchdEToiNARoSNCR4SOCB0ROiJ0ROiI0BGhI0JHhI4IHRE6InRE6Mi4Z/jznH+0xmk8Xut3gy46InRE6IjQEaEjQkeEjggdEToidEToiNARoSNCR4SOCB0ROiJ0ROiI0BGhI0JHhI4IHRE6InRE6IjQEaEjQkeEjggdEToidEToiNARoSNCR4SOCB0ZPIFtuOiI0BGhI0JHhI4IHRE6InRE6IjQEaEjQkeEjggdEToidEToiNCRDexBBl0OjJSaAAAAAElFTkSuQmCC"
    },
    "name": "image_crop"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoLeft px (mode=box)
yNoTop px (mode=box)
modeNoratio, box or trimratio
filesNoOr several files: [{fileName, fileContent (base64)}]
ratioNoRatio for mode=ratio1:1
widthNoWidth px (mode=box)
heightNoHeight px (mode=box)
fileNameNoFile name with extension, e.g. report.pdf
fileContentNoThe file as base64 (a data: URI is fine)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / height / minimum
      Added value: +0
    • addedInput schema / properties / width / minimum
      Added value: +0
    • addedInput schema / properties / x / minimum
      Added value: +0
    • addedInput schema / properties / y / minimum
      Added value: +0
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations cover only the safety profile (readOnly, idempotent, openWorld); the description adds genuinely new behavioral facts — server-side execution, immediate file deletion with nothing stored, a 25 calls/day free tier and $0.002 paid rate via x402. It stops short of describing what the response looks like (cropped file, base64, URL) or how billing errors surface.

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?

Three sentences, front-loaded with the core capability, then privacy and pricing facts. No filler or repeated content; each sentence contributes distinct information.

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

Completeness4/5

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

For a 9-parameter, zero-required tool with no output schema, the definition covers modes, data handling, and cost. The main residual gap is the return value — the agent cannot tell whether it receives base64 inline, a download URL, or a batch structure when using the files array.

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 every parameter is already documented, including mode, ratio enum, x/y/width/height, and the batch files array. The description's ratio list and mode names restate the schema rather than adding syntax or interaction rules (e.g. whether files overrides fileName/fileContent).

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 and resource ("Crop images") and enumerates all three operating modes with the exact ratio set, so an agent knows precisely what it does and can distinguish it from pdf_crop or image_resize by the "images" scope and cropping semantics.

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?

The three modes (ratio, box, trim) imply which parameter set applies, but there is no explicit when-to-use guidance, no mention of when to prefer image_resize or pdf_crop, and no stated prerequisites for the x402 payment path beyond a URL.

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