Skip to main content
Glama

Сжать фото

compress_image

Сжимает фото (JPG, PNG, WEBP, HEIC). Одно фото — файл, несколько — ZIP-архив. file_urls: публичные URL фото. level: light (высокое качество) | medium (по умолчанию, до 2560 px) | strong (до 1600 px). target_kb: сжать до размера в КБ (10–50000), тогда level не используется.

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": "compress_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNomedium
file_urlsYes
target_kbNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/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 description's job is smaller. It still adds substantive behavior beyond them: the result is a single file or a ZIP depending on input count, and each level caps resolution at a stated pixel size. It does not say that the public URLs are fetched over the network, which is exactly what openWorldHint implies but a caller should still be told.

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?

Four short, front-loaded fragments, one per concern: formats, output shape, file_urls, level, target_kb. No filler sentences and no repetition of the title.

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 3-parameter tool with an output schema, the description covers formats, output shape, all parameters and the mode precedence — enough to call it correctly. Minor omissions remain: how many URLs can be batched, and whether the source images are downloaded from those public URLs.

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

Parameters5/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 does: file_urls is documented as public URLs, level is given three named values with quality/resolution meaning and a default, and target_kb is given a 10–50000 range plus its override relationship to level. This adds information that appears nowhere in the schema, including an enum that the schema lacks.

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 ('Сжимает фото') plus the supported formats (JPG, PNG, WEBP, HEIC), so an agent knows exactly which inputs qualify. It also names the output shape (single file vs ZIP for multiple photos), which distinguishes it from a plain conversion sibling like heic_to_jpg.

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?

Gives a real selection rule between the two compression modes: level for quality/resolution presets and target_kb for a size target, with an explicit precedence statement ('тогда level не используется'). It stops short of saying when to call this versus resize_image or the format converters, so no explicit alternatives or exclusions.

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.