Skip to main content
Glama
PowerTokens Video Studio

PowerTokens Video Studio

Official

estimate_cost

Estimates the cost of generating a video at published PowerTokens prices before you commit. Set model, duration, and resolution to see your final bill.

Instructions

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

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": "estimate_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNowan3.0-video
duration_sNo
resolutionNo720p

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.15.0
    • addedInput schema / properties / model
      Added value: +{
      +  "default": "wan3.0-video",
      +  "title": "Model",
      +  "type": "string"
      +}
  2. First observedv1.11.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and mostly doesn't: it never says whether calling it consumes tokens or quota, whether it is read-only, whether it is deterministic, or whether rates vary by model. 'Your bill is final' gestures at pricing authority but is ambiguous — it undercuts the word 'Estimate' without clarifying behavior.

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

Conciseness3/5

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

It is a single short sentence with no padding and the caveat is placed after the core claim, which is reasonable front-loading. However, brevity here comes from omission rather than efficiency, so it reads as under-specified rather than tight.

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

Completeness2/5

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

An output schema exists, so return values needn't be described, but for a zero-required-param cost estimator with three undocumented inputs and no annotations, the one-line description leaves an agent unable to know what the estimate means or when to trust it. The 'bill is final' phrasing is the only behavioral content and it is cryptic.

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

Parameters1/5

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

Schema description coverage is 0% across three parameters with non-obvious fields like duration_s and resolution, and the description adds no meaning to any of them — no units, no valid ranges, no defaults, no explanation of how model or resolution affect the estimate. This is the dimension where the text most clearly fails.

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

Purpose3/5

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

The verb 'Estimate the cost' is concrete, but the resource is left implicit — nothing says the estimate covers video generation, and no sibling (generate_video, list_models) is referenced to anchor it. An agent can guess from the model/duration_s/resolution params, but the description alone doesn't distinguish it from a general pricing lookup.

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

Usage Guidelines2/5

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

No when-to-use guidance at all: no statement that this should be called before generate_video, no mention of whether it is required, and no alternatives named among the six siblings. The only hint of context is the pricing caveat, which is not usage guidance.

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