Skip to main content
Glama
Sign In
PowerTokens Video Studio

PowerTokens Video Studio

Official
by PowerTokens
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_models

Lists supported video models with duration and resolution limits plus short descriptions so you can compare options before generating videos.

Instructions

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_models"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.15.0

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the burden. It usefully discloses the shape of the payload (per-model duration/resolution limits and a short description) and rules out pricing, but says nothing about read-only safety, authentication, caching, or whether the list is static or account-dependent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with no filler; the resource is front-loaded and the '(no prices)' scope note is placed where it prevents a wrong assumption. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and zero input parameters, the description only needs to convey purpose and scope, which it does. It could be marginally stronger by naming estimate_cost as the companion for pricing, but nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to clarify and the baseline is 4. The description correctly implies a no-filter, return-everything listing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('List') and resource ('supported video models') and states exactly what each entry contains (duration/resolution limits, short descriptions). The parenthetical '(no prices)' scopes it away from estimate_cost, though it stops short of naming that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is a discovery step before generate_video or estimate_cost, and '(no prices)' signals where to go for cost data. There is no explicit when-to-use statement or named alternative, leaving the agent to infer the workflow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools