Skip to main content
Glama

Image To Video Price

image_to_video_price

Calculate the cost of an image-to-video generation job before running it, factoring in model, resolution, frames, FPS, steps, and reference-file surcharges.

Instructions

Calculate price for image-to-video generation.

For reference mode, pass the number of reference files the job will carry (not the files themselves). Surcharges do not stack: the highest applies, so 4 images plus a video is x3, not x6.

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": "image_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)
ref_audios_countNoHow many ref_audios the job will send. No surcharge
ref_images_countNoHow many ref_images the job will send. More than 2 doubles the price
ref_videos_countNoHow many ref_videos the job will send. Any video triples the price

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.3

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description must carry behavioral weight, and it does disclose a non-obvious pricing rule: surcharges do not stack, and the highest applies, with a concrete worked example ('4 images plus a video is x3, not x6'). That is a genuine addition beyond the schema, which only says more than 2 images doubles the price and any video triples it. It still does not state that the call is a read-only calculation with no job created, so it falls short of the top tier.

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?

Two short paragraphs: the purpose first, then the reference-mode and surcharge caveat. Every sentence, including the '4 images plus a video is x3, not x6' example, carries information that prevents a wrong calculation.

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 9-parameter pricing tool with a full output schema and complete schema descriptions, the description covers the purpose and the one behavior that could trip an agent up (surcharge stacking). Remaining gaps, such as which of the quality parameters (fps, steps, width, height) actually affect the price, are minor, since the schema defers those limits to the model list.

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?

Schema coverage is 100%, so the baseline is 3, and the description improves on that by clarifying that reference counts are passed rather than files, and by explaining how the per-reference-count surcharges combine. The stacking rule is meaning that cannot be derived from the schema fields alone.

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 opens with a specific verb+resource: 'Calculate price for image-to-video generation.' This makes it clearly the pricing counterpart to the generation tool of the same name. It does not explicitly name a sibling or exclusion, but the phrase 'Calculate price' combined with the title distinguishes it adequately from image_to_video.

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?

The description tells the agent how to use reference mode ('pass the number of reference files the job will carry (not the files themselves)'), which is a real usage instruction. However, it gives no explicit statement of when to choose this tool over alternatives, such as text_to_video_price or audio_to_video_price, leaving the agent to infer the selection from the tool name.

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