Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
VIMAX_HOMENoPath to ViMax checkout (added to sys.path at first job)~/projects/ViMax
VIMAX_MCP_LOGNoLog levelINFO
GOOGLE_API_KEYYesForwarded to ViMax image/video generators
VIMAX_JOBS_DIRNoPer-job output root$VIMAX_HOME/.working_dir/jobs
VIMAX_MCP_HOSTNoSSE bind host127.0.0.1
VIMAX_MCP_PORTNoSSE bind port7801
MINIMAX_API_KEYYesForwarded to ViMax chat model
VIMAX_QUOTA_FILENoPersisted daily-quota counter$VIMAX_HOME/.working_dir/quota.json
VIMAX_MCP_TRANSPORTNostdio or sse (CLI flag overrides)stdio

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
submit_idea2videoA

Submit an idea-to-video job. Returns immediately with a job_id; poll get_job_status for progress.

submit_script2videoC

Submit a script-to-video job. Returns immediately with a job_id; poll get_job_status for progress.

get_job_statusB

Get current state, progress, and error list for a submitted job.

list_artifactsB

List files produced by a job. kind ∈ final | frames | intermediate | all.

cancel_jobA

Cancel a running or queued job. Working_dir is preserved for inspection.

get_quotaA

Today's daily quota usage for chat / image / video providers (UTC day).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a distinct purpose: submitting jobs (two types), canceling, status polling, artifact listing, and quota checking. No overlap or ambiguity.

Naming Consistency4/5

All tools use lowercase with underscores and follow a verb_noun pattern (e.g., cancel_job, get_job_status). Minor inconsistency: 'submit_idea2video' uses '2' instead of 'to', but otherwise consistent.

Tool Count5/5

6 tools is a well-scoped set for a video generation job server, covering submission, monitoring, cancellation, output retrieval, and quota checking without being overwhelming.

Completeness3/5

Core lifecycle is covered (submit, cancel, status, artifacts), but missing a way to list all jobs or query by criteria, which may require external tracking of job_ids.

Maintenance

ActivityInactive
ResponsivenessNo issues