Skip to main content
Glama
PowerTokens

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
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
check_keyA

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

estimate_costC

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

generate_videoC

Submit a generation; it may take up to an hour. If the result is unclear, check the original task first; never regenerate automatically.

resume_videoB

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

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 4 tools

Disambiguation5/5

Each tool has a distinct purpose: checking local key configuration, estimating cost, submitting a generation, and resuming/downloading an existing task. The descriptions make the boundaries between generate and resume especially clear, with no apparent overlap.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: check_key, estimate_cost, generate_video, resume_video. There are no mixed conventions or vague verbs.

Tool Count5/5

Four tools are well-scoped for a focused video generation service, covering setup awareness, cost estimation, submission, and retrieval. No tool feels redundant or missing for the core workflow.

Completeness4/5

The core lifecycle is covered: check key status, estimate cost, generate video, and resume/check an existing task. Minor gaps exist, such as no task listing or cancellation, but agents can likely work around these using returned task IDs.

Maintenance

ActivityMaintained
ResponsivenessNo issues