Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MAX_IMAGE_SIZENoMax image size in bytes10485760
OPENROUTER_MODELNoAI model to useanthropic/claude-3.5-sonnet
OPENROUTER_API_KEYYesYour OpenRouter API key

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
analyze_imageC

Analyze an image using AI vision models. Supports file paths and URLs.

list_modelsB

Get list of available AI vision models for vision analysis

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: analyze_image performs image analysis using vision models, while list_models retrieves available models. There is no overlap or ambiguity between these functions.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern (analyze_image, list_models) with clear, descriptive names that align well with their functions. The naming is uniform and predictable.

Tool Count2/5

With only 2 tools, the server feels thin for a vision analysis domain. While it covers basic analysis and model listing, typical vision servers might include additional operations like batch processing, model details, or image preprocessing, making this count borderline minimal.

Completeness2/5

The tool surface is severely incomplete for vision analysis. It lacks essential operations such as getting model details, preprocessing images, batch analysis, or managing analysis results, which could lead to agent failures in complex workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues