Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Upscale video

upscale_video

Upscale a low-resolution video to 2x for final delivery. Use the standard precision engine or the FLUX upscaler, with an optional creative detail pass. Returns a served URL.

Instructions

Upscale a video to higher resolution (2x) for final delivery. Paid render; returns the served URL. Two engines: the default ('standard') is the safe precision upscaler; engine:'flux' is the FLUX 3 video upscaler (1080p/2K/4K) with an optional mode:'creative' detail-enhancement pass — pick it when the user asks for the FLUX upscaler or wants added detail rather than a faithful enlargement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoFLUX only — 'creative' turns on its detail-enhancement pass; default precise
videoYesthe source video URL
engineNodefault 'standard', the precision upscaler. 'flux' = the FLUX 3 video upscaler

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.256
    • changedInput schema / properties / engine / description
      Previous value: -"default topaz. 'flux' = the FLUX 3 video upscaler"New value: +"default 'standard', the precision upscaler. 'flux' = the FLUX 3 video upscaler"
    • changedInput schema / properties / engine / enum
      Previous value: -[
-  "topaz",
-  "flux"
-]New value: +[
+  "standard",
+  "flux"
+]
  2. Changed2 schema fields changedv0.1.249
    • addedInput schema / properties / engine
      Added value: +{
+  "description": "default topaz. 'flux' = the FLUX 3 video upscaler",
+  "enum": [
+    "topaz",
+    "flux"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / mode
      Added value: +{
+  "description": "FLUX only — 'creative' turns on its detail-enhancement pass; default precise",
+  "enum": [
+    "precise",
+    "creative"
+  ],
+  "type": "string"
+}
  3. Changed1 schema field changedv0.1.161
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "jobId": {
-      "description": "the render job id — poll get_job with this id to resume or inspect",
-      "type": "string"
-    },
-    "model": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "the product-facing label of the model that rendered it"
-    },
-    "raw": {
-      "description": "the raw job result payload (e.g. images[] for carousel template ads)"
-    },
-    "stillRendering": {
-      "description": "true when the render is still in progress — keep polling get_job with jobId",
-      "type": "boolean"
-    },
-    "url": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "the served URL of the finished media (absent/null while still rendering)"
-    }
-  },
-  "type": "object"
-}New value: +null
  4. Addedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the agent knows this is a paid, non-idempotent mutation. The description adds valuable context beyond that: it's a paid render, it returns a served URL, and the 'flux' engine has an optional 'creative' detail-enhancement pass. It doesn't detail failure modes or cost specifics, but the key behavioral traits are disclosed.

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?

Three sentences with no filler. The core action and outcome are front-loaded, and the engine/mode guidance is packed into the remaining sentences. Every clause 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 3-parameter tool with 100% schema coverage and no output schema, the description covers the action, the paid nature, the return value, and the engine-selection logic. It doesn't describe the output format in detail, but since there's no output schema, a brief note on the served URL is sufficient. The only minor gap is not stating what happens if 'mode' is used with the 'standard' engine, though the schema's 'FLUX only' note covers that.

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 description coverage is 100%, so the schema already documents all three parameters. The description adds meaning by explaining the practical difference between 'standard' and 'flux' engines and by clarifying that 'mode' is FLUX-only and 'creative' turns on a detail-enhancement pass. This goes beyond the schema's enum labels.

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?

The description states a specific verb ('Upscale'), a resource ('video'), and a concrete outcome ('to higher resolution (2x) for final delivery... returns the served URL'). It also distinguishes the two engines, which separates it from sibling video tools like clip_video, edit_video, and reframe_video.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says when to use the default 'standard' engine (safe precision upscaler) and when to pick 'flux' (when the user asks for the FLUX upscaler or wants added detail rather than faithful enlargement). It also flags that this is a paid render, which is a clear usage consideration.

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

Deploy Server

Other Tools