Skip to main content
Glama
IA-Programming

MCP Image Server

by IA-Programming
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
fetch_imagesA
Fetch and process images from URLs or local file paths, returning them in a format suitable for LLMs.

This tool accepts a list of image sources which can be either:
1. URLs pointing to web-hosted images (http:// or https://)
2. Local file paths pointing to images stored on the local filesystem (e.g., "C:/images/photo1.jpg")

For a single image, provide a one-element list. The function will process images in parallel
when multiple sources are provided. Images that exceed the size limit (1MB) will be automatically 
compressed while maintaining aspect ratio and reasonable quality.

Args:
    image_sources: A list of image URLs or local file paths. For a single image, provide a one-element list.
    
Returns:
    A list of Image objects or None values (if processing failed) in the same order as the input sources.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
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

TDQS

A4.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'fetch_images' has a clearly defined and distinct purpose that cannot be confused with any other tool in this server.

Naming Consistency5/5

The single tool name 'fetch_images' follows a clear verb_noun pattern, and with only one tool, there is perfect consistency. No naming conventions can conflict when only one tool exists.

Tool Count2/5

A single tool is generally too few for most server purposes, creating a thin surface that limits functionality. While this tool handles image fetching and processing well, the server's scope as an 'Image Server' suggests potential gaps that would require additional tools for comprehensive image operations.

Completeness2/5

For an 'Image Server' domain, having only a fetch/processing tool leaves significant gaps. There are no tools for image manipulation (resize, crop, filter), analysis (object detection, metadata extraction), or management (list, delete, organize images), making the surface severely incomplete for typical image-related workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources