Skip to main content
Glama

Video Upscale

video_upscale

Upscale a video to higher resolution.

Takes a video and upscales it using AI models for enhanced quality. Accepts videos as:

  • Public URLs (recommended, and the ONLY way in for a file of your own - chat clients do not pass files through to tools)

  • Data URIs or raw base64 (for callers that already hold the bytes)


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": {
      "video": "<video>",
      "model": "<model>"
    },
    "name": "video_upscale"
  }
}

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
videoYesVideo as URL, data URI (data:video/mp4;base64,...), or base64 string. URLs are recommended to avoid base64 context bloat.
webhook_urlNoHTTPS URL for deAPI to call when this job finishes. Notifies your own systems; the tool still returns the result here
webhook_secretNo32-255 char key deAPI signs the callback with (HMAC-SHA256). Needs webhook_url. A secret given in chat stays in the transcript

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does disclose substantive constraints: per-model input resolution caps (≤1.03Mpx, side ≤1344), per-model duration limits (11s/20s/15s), and the fixed-vs-variable scale behavior. It omits whether the call is asynchronous/job-based (only implied by the webhook parameters and the check_job_status sibling), expected latency, and cost implications.

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?

Front-loaded with the one-sentence purpose, then a well-structured bulleted model table, so an agent can scan the decision-relevant constraints immediately. There is mild redundancy — the base64 context-bloat rationale appears in both the description and the video parameter's schema text — but no 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 5-parameter job-submission tool with an output schema, the description covers input modes and per-model limits well enough to invoke correctly. The main remaining gap is the absence of any advice on choosing among the three required models (speed vs. quality vs. output factor) and no statement that this is a long-running job.

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 already 100%, so the baseline is 3; the description earns the step up by annotating the `model` parameter with per-model resolution and duration constraints that the schema's one-line 'Video upscaling model name' does not convey. The scale-versus-fixed-factor rule is restated from the schema rather than extended, limiting further credit.

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 ('Upscale a video to higher resolution') and lists the concrete models available, so an agent knows exactly what operation this performs. It does not, however, differentiate itself from close siblings such as image_upscale or video_upscale_price, so the agent must infer the boundary from the name alone.

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 useful input-channel guidance — public URLs are recommended and are stated to be the only way to submit your own file, with base64 reserved for callers already holding bytes. But there is no guidance on when to pick this tool versus video_upscale_price, image_upscale, or the video_to_* siblings, and no guidance on which of the three required model choices to prefer.

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.