Skip to main content
Glama
Sign In
Image MCP

Image MCP

by Expert-Integrado
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Converter/redimensionar imagem

convert_image

Convert image format (PNG, JPEG, WebP, AVIF), resize dimensions, or adjust compression quality — all locally without any API.

Instructions

Converte o formato (png/jpeg/webp/avif) e/ou redimensiona uma imagem local, sem usar API (grátis e instantâneo). Também serve para comprimir (parâmetro quality).

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": {
      "image": "<image>"
    },
    "name": "convert_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYesCaminho absoluto da imagem de entrada
widthNoLargura máxima em px (mantém proporção, nunca amplia)
formatNoFormato de saída. Omitido = mantém o original
heightNoAltura máxima em px (mantém proporção, nunca amplia)
outputNoCaminho de saída. Omitido = mesma pasta, mesmo nome com sufixo/extensão novos
qualityNoQualidade/compressão para jpeg/webp/avif (padrão do sharp: 80)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden. It reveals key behavioral traits: local processing (no API), free, instant. It mentions compression via quality parameter. However, it omits that resizing never upsamples (present in schema but not description) and does not discuss output naming or file overwrite behavior.

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?

Two concise sentences front-load the main purpose (format conversion and resize) and then add compression. Every phrase earns its place; no fluff.

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 conversion tool with no output schema, the description covers the main capabilities and a key benefit (no API, free). It lacks details on output behavior (e.g., overwrite, naming) but schema covers path parameters. Overall, sufficient for typical use.

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 coverage is 100%, so parameters are well-documented in the schema. The description merely restates that the tool can convert format, resize, and compress (quality). It adds no new semantic information beyond the schema.

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?

The description clearly states the tool converts format (png/jpeg/webp/avif), resizes, and compresses local images. It distinguishes itself from sibling tools like edit_image (editing) and generate_image (creation) by focusing on conversion/resize/compress without API.

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 implies use for local, instant, free conversion/resize/compression without an API. It does not explicitly state when not to use (e.g., for editing or generation), but the context of siblings and the tool's purpose provides implicit guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools