Skip to main content
Glama

Image Resize API - width, height or percent

image_resize
Read-onlyIdempotent

Resize 1-30 images by width, height (aspect kept) or percent, Lanczos quality; exact=true stretches to width x height. GPS/EXIF removed. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.003 per call via x402 at https://radarbg.com/x402/image-resize.

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": {
      "width": 60,
      "fileName": "sample.png",
      "fileContent": "iVBORw0KGgoAAAANSUhEUgAAAHgAAABQCAIAAABd+SbeAAAA6klEQVR4nO3cQQ2DABAAwdKgg1cFVQIykIOEyqiIisFDKdsQZv6XXDb3vmFa3jeOd//3AlchdEToiNARoSNCR4SOCB0ROiJ0ROiI0BGhI0JHhI4IHRE6InRE6Mi4Z/jznH+0xmk8Xut3gy46InRE6IjQEaEjQkeEjggdEToidEToiNARoSNCR4SOCB0ROiJ0ROiI0BGhI0JHhI4IHRE6InRE6IjQEaEjQkeEjggdEToidEToiNARoSNCR4SOCB0ZPIFtuOiI0BGhI0JHhI4IHRE6InRE6IjQEaEjQkeEjggdEToidEToiNCRDexBBl0OjJSaAAAAAElFTkSuQmCC"
    },
    "name": "image_resize"
  }
}

Input Schema

NameRequiredDescriptionDefault
exactNoUse exactly width x height
filesNoOr several files: [{fileName, fileContent (base64)}]
widthNoWidth in px (max 10000)
heightNoHeight in px (max 10000)
percentNoOr scale in percent (1-400)
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. Changed3 schema fields changed
    • addedInput schema / properties / height / minimum
      Added value: +0
    • addedInput schema / properties / percent / minimum
      Added value: +0
    • addedInput schema / properties / width / minimum
      Added value: +0
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so safety is largely covered. The description does add real context beyond that: GPS/EXIF metadata is stripped, processing happens server-side, files are deleted immediately with nothing stored, and there is a per-IP daily quota with per-call pricing. A 3 fits because it adds context without going beyond what's already covered.

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?

Capability is front-loaded in the first clause, followed by behavioral and cost information. It is a single dense run-on sentence chain using semicolons, which packs a lot in but slightly hurts scannability.

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?

With 7 optional parameters, no required fields, and no output schema, the description covers inputs, batch limits, privacy behavior, and cost thoroughly. The remaining gap is the return format (presumably base64 file content), which an agent must guess at.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds genuinely new meaning: width and height preserve aspect ratio (schema never says this), while exact=true stretches to width x height. It also frames percent as an alternative to width/height, clarifying that these are mutually exclusive modes rather than cumulative parameters.

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 (resize images) plus every operating mode: width, height with aspect kept, percent, and exact=true stretching to width x height, with a batch size of 1-30. An agent can tell this apart from sibling operations like image_crop, image_compress, or image_convert from the description alone.

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?

The description makes the mode-selection decision explicit (width vs height-with-aspect vs percent vs exact-stretch) and gives practical context such as the 1-30 image batch limit, free 25 calls/day per IP, and paid x402 pricing. It stops short of naming alternatives or stating when not to use it, so it earns a 4 rather than 5.

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