Skip to main content
Glama

Audio To Video Price

audio_to_video_price

Calculate price for audio-to-video generation.


Available models:

  • Ltx2_5_22B_Dist_INT8: size=512-1344x512-1344, fps=24 (fixed), frames=49-241, w/h rounded down to a multiple of 64, ≤1.03Mpx, side≤1344, aspect≤2, audio2video audio=1-10s, no negative_prompt

  • Ltx2_3_22B_Dist_INT8: size=512-1024x512-1024, fps=24 (fixed), frames=49-241, audio2video audio=1-11s, no negative_prompt

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": "audio_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 (optional; 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 observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations to fall back on, the description carries the full burden and does substantial work: it discloses per-model size ranges, fixed fps=24, frame ranges, the round-down-to-multiple-of-64 behavior, the ≤1.03Mpx / side≤1344 / aspect≤2 caps, audio duration limits, and that negative_prompt is unsupported. It stops short of stating that this is a read-only, no-side-effect estimate and says nothing about pricing units or currency, which leaves a small gap.

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?

One front-loaded purpose sentence followed by a compact, uniformly formatted per-model bullet list; no filler prose. It is somewhat dense and repeats the constraint vocabulary per model, but that repetition aids scanning rather than padding.

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?

For a six-parameter pricing tool with an output schema handling returns and no annotations, the definition supplies the constraint knowledge an agent needs to build valid inputs. The remaining hole is that the model list is the only required parameter's domain description and is not marked as such, so an agent could miss that `model` must be one of exactly those two names.

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%, so the baseline is 3, and the description genuinely adds the model-specific limits that the schema merely points to with "see the model list". However it covers only size/frames/audio duration, leaving the `steps` parameter with no stated per-model bounds and never clarifying which parameters are optional or what defaults apply.

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 audio-to-video generation" gives a specific verb (calculate price) and resource (audio-to-video generation), which cleanly separates it from the sibling generation tool audio_to_video and from the other *_price tools. It does not explicitly say it is an estimate-only call, but the verb plus the naming pattern makes the distinction inferable.

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?

There is no explicit when-to-use or when-not-to-use statement, and no mention of pairing with audio_to_video to actually produce the video. Usage is only implied by the price-calculating purpose and by the per-model constraint list, which tells the agent what inputs will be accepted.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.