A
licenseA
qualityB
maintenanceEnables file conversion between 690+ formats (image, video, audio, document, data, font, ebook, archive) using an MCP server, with no API key or signup required.
Last updated
2
263
4
MIT
Pixel Agent
Server Details
Convert images to PNG, JPEG, WebP, or AVIF through one public remote MCP tool.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A3.9/5.0
Tool DescriptionsA
Average 4/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
With only one tool available, there is no possibility of confusion between tools. The purpose of convert_image is clear and unambiguous.
Naming Consistency5/5
The single tool name follows a clear verb_noun pattern and accurately describes its function. Consistency is inherent with only one tool.
Tool Count2/5
The server has only one tool, which is too few for a server named 'Pixel Agent' that suggests a broader image manipulation scope. This will limit agents to a single, narrow operation.
Completeness2/5
The tool covers only format conversion, omitting common image operations like resizing, cropping, or metadata inspection. This leaves significant gaps that will prevent agents from accomplishing many image-related tasks.
Available Tools
1 toolconvert_imageConvert imageARead-onlyIdempotentInspect
Convert one base64-encoded image to PNG, JPEG, WebP, or AVIF. Use the REST API for source images larger than 5 MB.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| format | Yes | ||
| quality | No | Optional for JPEG, WebP, and AVIF. | |
| filename | No | Optional original filename used to derive the result name. | |
| image_base64 | Yes | Base64-encoded source image bytes. Maximum decoded size: 5 MB. | |
| input_mime_type | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| bytes | Yes | |
| filename | Yes | |
| mime_type | Yes |
Tool Definition Quality
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly and idempotent behavior, and the description does not contradict them. The description adds the 5 MB limit, but that is also present in the schema. It does not disclose additional side effects or state-change behavior beyond annotations.
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?
The description is two short sentences, front-loaded with the core purpose and followed by a single actionable constraint. Every word earns its place with no redundancy.
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 an output schema and annotations present, the description covers the essential behavior and the key size limitation. It could mention the return format explicitly, but the output schema likely fills that gap. The description is sufficient for a straightforward conversion tool.
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 60%; the description reinforces that the source is base64 and lists target formats, complementing the schema. However, it does not fully compensate for undocumented parameters like input_mime_type, though enums provide some meaning. The description adds moderate value 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 a base64-encoded image to one of four specific formats (PNG, JPEG, WebP, AVIF). It uses a specific verb and resource, making the purpose immediately clear even without sibling tools.
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 explicitly tells users to use the REST API for source images larger than 5 MB, providing a clear when-not-to-use condition. It could mention more contextual use cases, but the size threshold is a concrete and actionable guideline.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityCmaintenanceMCP server for converting images to WebP and AVIF formats with batch processing and parallel execution.Last updatedMIT
- AlicenseCqualityDmaintenanceImage Tools MCP is a Model Context Protocol (MCP) service that retrieves image dimensions and compresses images from URLs and local files using the TinyPNG API. It supports converting images to formats like webp, jpeg/jpg, and png, providing detailed information on width, height, type, and compressiLast updated24810MIT
- Alicense-qualityDmaintenanceAn MCP server for converting images to AVIF and WebP formats using ImageMagick, with batch conversion and quality control.Last updated431MIT