Skip to main content
Glama

Video Upscale Price

video_upscale_price

Calculate the price for upscaling a video using a chosen model, with input as the video itself or its width, height, and duration.

Instructions

Calculate price for video upscaling.

Pass the video itself, or its width, height and duration.

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

Input Schema

NameRequiredDescriptionDefault
modelYesVideo upscaling model name
scaleNoUpscale factor, only for models with a 'scale' range in the model list (FlashVSR_Tiny: 2-4). Unset, those models use their smallest factor. Models without a range have a fixed factor (e.g. RealESRGAN_Vid_x4) and refuse this field
videoNoVideo to quote (URL, data URI or base64); its size and length are read from it. Or pass width, height and duration instead
widthNoVideo width in pixels. Provide width+height to estimate without uploading a file.
heightNoVideo height in pixels. Provide width+height to estimate without uploading a file.
durationNoVideo length in seconds; the price is linear in frames. Required unless video is given

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.3

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden, and it does disclose the key operational trait: you can quote either from an uploaded video or from dimensions alone, implying a pure calculation with no processing side effects. What it omits is currency/units and whether supplying a video incurs any upload cost, which keeps it below a 5.

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 sentences, zero filler, with the purpose front-loaded and the input-mode rule immediately after. Nothing is redundant or buried.

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?

An output schema exists, so return values need no explanation, and the schema fully documents all six parameters. The description covers both input paths and the tool's purpose, leaving only minor gaps such as pricing currency and how the resulting figure relates to an actual upscale job.

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 schema already documents model, scale, width, height and duration, including the model-scaling rules and the 'required unless video is given' constraint. The description only restates the same either/or input mode at a higher level, adding no format or edge-case detail beyond it. Baseline 3 applies.

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?

States a specific verb and resource: "Calculate price for video upscaling." An agent can immediately tell this is a quoting tool rather than the upscale action itself. It doesn't explicitly name video_upscale as the sibling that performs the work, so it stops short of full differentiation.

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 implied (call this to get a cost estimate before running video_upscale), but the description never says when to use it versus video_upscale, nor that the price should be checked before submitting a job. No exclusions or prerequisites are given.

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