Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Image Converter

ImageConverter
Read-only

Image Converter: Image Converter transforms images between formats. Convert HEIC from iPhones, modern WebP and AVIF formats, or classic PNG, JPG, GIF, and TIFF. Includes optional resizing and quality control, and paid plans also get the pixel width and height of the converted file. (Cost: 10 credits)

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>",
      "outputFormat": "<outputFormat>"
    },
    "name": "ImageConverter"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYesUpload an image file to convert (supported formats: HEIC, HEIF, AVIF, WebP, PNG, JPG, GIF, TIFF, BMP, PDF, SVG)
qualityNoOutput quality (applies to jpg/webp)
maxWidthNoMaximum width in pixels (maintains aspect ratio)
maxHeightNoMaximum height in pixels (maintains aspect ratio)
outputFormatYesTarget format

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, open-world, non-destructive behavior. The description adds useful operational context beyond the annotations: a 10-credit cost and that paid plans return pixel dimensions, which affects planning and output expectations.

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?

The description is front-loaded and compact, covering purpose, formats, features, and cost. It has slight redundancy in repeating 'Image Converter' as a prefix, but no major waste.

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 annotations, a full input schema, and an output schema, the description provides enough context for calling the tool: supported formats, resizing/quality, cost, and plan-dependent output. Minor gaps remain around outputFormat allowable values and file limits.

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 the schema already documents image, quality, maxWidth, maxHeight, and outputFormat. The description only adds a high-level mention of optional resizing and quality control, without format/value details beyond what the schema provides.

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 states a specific verb and resource ('transforms images between formats') and enumerates supported formats plus optional resizing/quality. It is clear enough to identify the tool, though it does not explicitly mention sibling converters such as HEICConverter or WebPConverter to clarify routing.

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?

It supplies clear usage context: converting iPhone HEIC, WebP/AVIF, or classic formats, with optional resizing and quality control. It does not state exclusions or explicitly compare with specialized sibling converters, so it stops short of full when/when-not guidance.

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

All APIVerve toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources