Skip to main content
Glama
PowerTokens Video Studio

PowerTokens Video Studio

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
POWERTOKENS_API_KEYNoPowerTokens API key (optional; only needed to generate or resume videos)

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
check_keyA

Check the CLI key pool configuration (does not verify remote access).

list_modelsA

List supported video models with duration/resolution limits and short descriptions (no prices).

estimate_costC

Estimate the cost at published PowerTokens prices; your bill is final.

generate_videoB

Submit a generation (set model to Wan 3.0 / Prime, Seedance 2.0 Fast / 2.5, or kling v3); it may take up to an hour. If the result is unclear, check the original task first; never regenerate automatically. Call list_models for short descriptions.

resume_videoB

Check and download an existing task with its original key; nothing new is submitted.

compare_videosB

Submit one prompt to 2–3 models for comparison; each result is a separate resumable task. models is a comma-separated list of model IDs.

storyboardC

Split a script into a batch prompt spreadsheet

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

Disambiguation4/5

The core lifecycle is cleanly split: list_models, estimate_cost, generate_video, compare_videos, and resume_video each target a distinct step, and descriptions explicitly clarify boundaries (e.g. resume_video 'nothing new is submitted'). The weak points are storyboard, whose one-line description doesn't make clear how it relates to generation, and the implicit link between 'check the original task' in generate_video and resume_video, which an agent must infer.

Naming Consistency4/5

Six of seven tools follow a clean verb_noun snake_case pattern (list_models, estimate_cost, generate_video, compare_videos, check_key, resume_video). The exception is 'storyboard', a bare noun that breaks the pattern and, combined with its terse description, is the least predictable name in the set.

Tool Count5/5

Seven tools is well within the sweet spot for a focused media-generation server, and each one maps to a real workflow step (discover, price, generate, compare, batch, resume). No tool looks like filler.

Completeness4/5

The surface covers discovery, pricing, single generation, multi-model comparison, batch scripting, and retrieval of past tasks. Gaps remain around task management: there is no list/history tool to find prior task IDs and no cancel or delete operation, so agents that lose a task ID have no recovery path.

Maintenance

ActivityMaintained
ResponsivenessLimited data