Skip to main content
Glama

Text To Video Price

text_to_video_price

Calculate the cost of generating a video from text by entering a model and optional settings such as dimensions, frames, FPS, and steps before running the job.

Instructions

Calculate price for text-to-video generation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "model": "<model>"
    },
    "name": "text_to_video_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNoFrames per second (optional; limits per model, see the model list)
modelYesVideo generation model name
stepsNoNumber of inference steps. Limits per model (see the model list)
widthNoVideo width in pixels. Limits per model (see the model list)
framesNoNumber of video frames. Limits per model (see the model list)
heightNoVideo height in pixels. Limits per model (see the model list)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.3

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and says almost nothing: no indication that this is a non-mutating estimate, no mention of currency/units, required permissions, or what happens when optional parameters are omitted. Only the bare verb "calculate" hints at a read-only computation.

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

Conciseness4/5

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

A single front-loaded sentence with zero filler. It is concise, though the brevity reflects under-specification rather than tight editing of rich content.

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?

For a six-parameter pricing tool with no annotations, the description omits key context such as pricing units, whether defaults are applied for omitted optional parameters, and how the estimate relates to actually invoking text_to_video. Output schema coverage of return values is handled elsewhere, but input-side behavioral context is missing.

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

Parameters3/5

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

Schema coverage is 100% — all six parameters have their own descriptions including per-model limit notes — so the schema does the heavy lifting and a baseline 3 applies. The description adds no meaning beyond the schema, but none is needed.

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?

"Calculate price for text-to-video generation" names a specific verb (calculate) and resource (text-to-video generation price), making it distinguishable from the sibling text_to_video action tool. It does not explicitly state the contrast with siblings, but the verb/resource pairing is unambiguous.

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?

There is no guidance on when to use this versus text_to_video or the other *_price siblings — e.g., that this is a cost-estimation call to run before committing to a generation request. The agent must infer the workflow entirely from the name.

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