Skip to main content
Glama

Изменить размер фото

resize_image

Меняет размер фото (JPG, PNG, WEBP, HEIC, TIFF, BMP), формат сохраняется. Одно фото — файл, несколько — ZIP. file_urls: публичные URL фото. percent: масштаб в процентах (1–500; по умолчанию 50) — или width и/или height в пикселях. keep_aspect: сохранить пропорции (по меньшему масштабу). enlarge: разрешить увеличение (по умолчанию фото меньше заданного не растягиваются).

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": {
      "file_urls": "<file_urls>"
    },
    "name": "resize_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthNo
heightNo
enlargeNo
percentNo
file_urlsYes
keep_aspectNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is largely covered. The description does add real value beyond that: it states the output format is preserved, that a single photo returns a file and multiple return a ZIP, and that by default small images are not upscaled (enlarge=false).

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?

Purpose and format/output behavior are front-loaded in the first sentence, then each parameter gets a compact line with no filler. A couple of phrasings are very terse ("по меньшему масштабу") and the width/height line is thin, but nothing is wasted.

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 6-parameter non-read-only tool with an output schema present, the description covers the essentials: accepted formats, output packaging, all defaults, and the scaling semantics. Remaining gaps are edge-case interactions between percent and width/height and error behavior for unreachable URLs, which keep it from a 5.

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 0%, so the description carries the full burden and mostly delivers: it constrains percent to 1–500 with default 50, explains keep_aspect as scaling by the smaller factor, and clarifies enlarge=false means images smaller than the target are not stretched. Gaps remain for width/height (no ranges, no statement of what happens when they are combined with percent or with only one of them supplied).

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?

Opens with a specific verb+resource ("Меняет размер фото") and adds supported formats plus the guarantee that the format is preserved, which separates it from convert-style siblings like png_to_jpg. It does not explicitly distinguish resize from the visually overlapping siblings crop_image, rotate_image, or compress_image, so it stops short of a 5.

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 in-tool guidance on choosing the scaling mode ("percent ... — или width и/или height") and explains output packaging for one vs many photos. However, it never says when to pick resize_image over compress_image or crop_image, nor any prerequisites for the input URLs beyond "публичные".

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.