Skip to main content
Glama

HEIC в JPG

heic_to_jpg

Конвертирует фото HEIC/HEIF с iPhone в JPG. Одно фото — JPG, несколько — ZIP-архив. file_urls: публичные URL фото HEIC. compact: уменьшить до 2000 px. keep_metadata: сохранить данные съёмки (EXIF: дата, камера, геометка).

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

Input Schema

NameRequiredDescriptionDefault
compactNo
file_urlsYes
keep_metadataNo

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, openWorldHint=true, idempotentHint=false, destructiveHint=false, so the safety profile is covered. The description still adds genuinely useful behavior beyond that: the output shape depends on input count (one photo → JPG, several → ZIP) and metadata handling is opt-in. It says nothing about failure modes on non-HEIC input or fetch errors for unreachable URLs. With annotations carrying the safety profile, this is a solid 3.

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?

Four short lines with zero filler, front-loaded with the core action before the parameter notes. The terse list style is efficient, though the per-parameter fragments are not visually separated from the prose sentence describing output behavior.

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?

An output schema exists, so return-value documentation is unnecessary; the description nonetheless covers the one thing an agent must know about the return, namely the JPG-vs-ZIP branching. For a three-parameter conversion tool with annotations present, this is nearly complete, lacking only input limits and error expectations.

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 it discharges that for all three parameters: file_urls are public URLs to HEIC photos, compact downscales to 2000 px, keep_metadata preserves EXIF date/camera/geolocation. The only thing missing is any note on limits or multiple-URL ordering, so it is not a 5.

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 opens with a specific verb+resource pair ('Конвертирует фото HEIC/HEIF с iPhone в JPG'), which is unambiguous and the format names implicitly separate it from png_to_jpg, webp_to_jpg and jpg_to_png. It does not explicitly name an alternative or state the boundary case, so it stops just 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?

Usage is implied rather than stated: the agent learns that inputs must be public HEIC/HEIF URLs, which is a real prerequisite. There is no explicit 'use this when…' / 'do not use when…' guidance, and no mention of limits such as maximum file count or size, or when to pick resize_image/compress_image afterwards.

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.