Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
VISION_HOSTNoHost for streamable-http mode. Default: 127.0.0.1127.0.0.1
VISION_PORTNoPort for streamable-http mode. Default: 80008000
VISION_MODELNoDefault model. Default: glm-4v-plusglm-4v-plus
ZHIPU_API_KEYNoZhipu API key, used as fallback if VISION_API_KEY and OPENAI_API_KEY are not set.
OPENAI_API_KEYNoOpenAI API key, used as fallback if VISION_API_KEY is not set.
VISION_API_KEYNoAPI Key. Required. Fallback order: VISION_API_KEY → OPENAI_API_KEY → ZHIPU_API_KEY.
VISION_TIMEOUTNoRequest timeout in seconds. Default: 300300
VISION_BASE_URLNoOpenAI-compatible endpoint. Default: https://open.bigmodel.cn/api/paas/v4https://open.bigmodel.cn/api/paas/v4
VISION_MAX_FILESNoMaximum number of documents per request. Default: 44
VISION_TRANSPORTNoTransport mode: stdio or streamable-http. Default: stdiostdio
VISION_MAX_IMAGESNoMaximum number of images per request. Default: 44
VISION_MAX_VIDEOSNoMaximum number of videos per request. Default: 11
VISION_DOC_TOOL_TYPENoZhipu document parsing tool: lite (free), expert (better for PDF tables/formulas), prime (complex layout). Default: litelite
VISION_MAX_DOC_CHARSNoMaximum characters of parsed document text fed to model. Default: 500000500000
VISION_MAX_FILE_BYTESNoLocal document size limit. Default: 20 MiB20 MiB
VISION_MAX_IMAGE_BYTESNoLocal image size limit. Default: 20 MiB20 MiB
VISION_MAX_VIDEO_BYTESNoLocal video size limit. Default: 50 MiB50 MiB

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
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
vision_analyzeA

Analyze one or more images with a vision model.

Works for photos, screenshots, UI layouts, charts, plots, schematics, etc. For text extraction prefer vision_ocr.

Args: images: Image references. Each item may be an http(s) URL, a local file path, or a data:image/...;base64,... data URI. prompt: The question or instruction for the vision model. Be as specific as possible (e.g. "What does this chart show? List the axes and trends."). model: Optional model name override (e.g. glm-4.6v). Defaults to the server's configured VISION_MODEL. max_tokens: Optional cap on the response length. thinking: Enable the reasoning chain (Zhipu glm-4.6v+; ignored by other providers that don't support it). Useful for complex charts/docs.

Returns: The model's text answer.

vision_ocrA

Extract all text from one or more images (OCR via vision model).

Args: images: Image references (http(s) URL, local file path, or data URI).

Returns: The extracted text.

vision_videoA

Understand one or more videos with a vision model.

Args: videos: Video references. Each item may be an http(s) URL, a local file path (mp4/mov/avi/mkv/webm/...), or a data:video/...;base64 data URI. prompt: The question or instruction, e.g. "Summarize what happens in this video." / "At which second does the person enter the frame?". For temporal questions be explicit about time points. model: Optional model name override (e.g. glm-4.6v). Defaults to the server's configured VISION_MODEL. max_tokens: Optional cap on the response length. thinking: Enable the reasoning chain (Zhipu glm-4.6v+; ignored by other providers that don't support it). Useful for complex charts/docs.

Returns: The model's text answer.

vision_documentA

Ask questions about documents (pdf/doc/docx/xls/xlsx/ppt/pptx/txt/md/csv).

Great for reports, papers, spec sheets, and extracting data from complex tables and charts embedded in documents.

Args: files: Document references. Each item may be an http(s) URL, a local file path, or a data:application/...;base64 data URI. prompt: The question or instruction, e.g. "Summarize the key findings." / "What is the maximum value in the table on page 2?". model: Optional model name override (e.g. glm-4.6v). Defaults to the server's configured VISION_MODEL. max_tokens: Optional cap on the response length. thinking: Enable the reasoning chain (Zhipu glm-4.6v+; ignored by other providers that don't support it). Useful for complex charts/docs.

Returns: The model's text answer.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct input type: vision_analyze for images, vision_ocr for text extraction from images, vision_video for videos, and vision_document for documents. The description explicitly advises using vision_ocr over vision_analyze for text extraction, eliminating ambiguity.

Naming Consistency4/5

All tools follow a consistent vision_ prefix and use lowercase snake_case. However, vision_analyze uses a verb while vision_ocr, vision_video, and vision_document use nouns or acronyms, creating a minor inconsistency in part of speech.

Tool Count5/5

With 4 tools, the server is well-scoped for its domain of multimodal vision analysis. Each tool addresses a different input modality (images, OCR, videos, documents), leaving no obvious gaps while avoiding unnecessary bloat.

Completeness5/5

The set covers the core capabilities one would expect from a vision MCP server: general image analysis, OCR, video understanding, and document Q&A. No essential operations are missing for the stated purpose of analyzing visual content.

Maintenance

ActivitySlowing
ResponsivenessNo issues