Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WAN30_CONFIG_DIRNoChanges the directory used for credential storage when using file-based credential storage.
WAN30_ACCESS_TOKENNoAccepts a pre-issued access token for automation.

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
account_statusB

Available website credits and access to generation.

list_modelsC

Supported generation models.

get_modelC

Input options for the selected video model.

estimate_generationB

Quote credits before generation.

generate_videoA

Spend website credits on a text, first-frame or reference video. Confirm the estimate and reuse requestId on retries.

list_tasksC

Recent supported video tasks for this account.

get_taskB

Poll your video task for its status and download URL.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct step: account status (credits), model discovery (list/get), cost estimation, generation, and task tracking (list/get). The list/get pairs are standard and clearly separable, and estimate_generation vs account_status are distinguished by purpose (per-request quote vs overall balance).

Naming Consistency4/5

Six of seven tools follow a clean verb_noun convention (list_models, get_model, estimate_generation, generate_video, list_tasks, get_task). account_status breaks the pattern as a bare noun phrase, a minor deviation but still readable and consistent with the domain.

Tool Count5/5

Seven tools map to a complete, well-scoped workflow (credits -> model options -> estimate -> generate -> poll). No tool feels redundant or unnecessary for the stated purpose.

Completeness4/5

The core lifecycle from credit check through generation to download URL is fully covered, including pre-flight estimation and requestId-based retry guidance. Minor gaps exist around task lifecycle management (e.g., cancel/delete a task) that agents cannot perform.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues