Skip to main content
Glama

Video Upscale Price

video_upscale_price

Calculate price for video upscaling.

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


Available models:

  • FlashVSR_Tiny: input size=128-1344x128-1344, ≤1.03Mpx, side≤1344, video≤11s, scale=2-4x

  • RealESRGAN_Vid_x2: input size=128-1344x128-1344, ≤1.03Mpx, side≤1344, video≤20s

  • RealESRGAN_Vid_x4: input size=128-1344x128-1344, ≤1.03Mpx, side≤1344, video≤15s

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 observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does add real behavioral context by publishing per-model limits (max pixel count, side ≤1344, max duration 11/15/20s, fixed vs. ranged scale), which tells the agent which inputs will be rejected. But it never says whether this call itself is free/read-only, whether it creates a job, or that the result is an estimate only — a notable gap for a pricing tool.

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?

Purpose and input modes are front-loaded in two sentences, and the model matrix is a compact, scannable list. Some of the model limit text duplicates what the schema already says about 'scale', and the '---' separator is filler, but otherwise every line earns its place.

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 tool with no annotations but an existing output schema (so return values need not be explained), the description covers the model constraint matrix and both input paths adequately. It is only thin on billing/side-effect semantics and on how the estimate is computed beyond 'price is linear in frames', which lives in the schema rather than the description.

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 would be 3, but the description adds meaning the schema lacks: the enumerated model names with their individual input size, duration, and scale constraints, and the note that some models require scale while others refuse it. This materially improves correct selection of the 'model' and 'scale' parameters.

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

Purpose5/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'), which cleanly separates it from the sibling video_upscale that presumably performs the operation. An agent can tell from the description alone that this returns a quote, not an upscaled file.

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 sentence 'Pass the video itself, or its width, height and duration' gives the two viable input modes, which is useful calling guidance. However, it never states when to use this tool versus video_upscale (e.g. 'call before upscaling to check cost'), nor any prerequisite such as balance checks, so usage is only implied.

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.