Skip to main content
Glama

upscale_clip

Raises a clip's resolution to 1080p: pick simple resizing with sharpening for speed, or GPU LTX re-render for real detail.

Instructions

Bigger video. method "simple": resize to height with sharpening (seconds, any video). method "ltx": GPU, renders the same clip again with the LTX second pass to 1080p - real detail, but 30-50 min on a 4 GB card.

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>"
    },
    "name": "upscale_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
videoYes
heightNo
methodNosimple

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare this is a non-read-only, closed-world, non-destructive operation; the description adds substantial behavior beyond that — runtime estimates per method (seconds vs 30-50 minutes), a GPU requirement, and a quality expectation difference. These are exactly the cost/latency signals an agent needs before invoking a long GPU job. It does not say whether the source clip is preserved or what is returned.

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?

Two dense sentences, method-specific details front-loaded per branch, with no filler. The telegraphic opening ('Bigger video.') is slightly terse but not confusing. Every clause adds a distinct fact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and a mutation-style tool, the description should say what the caller gets back and whether the source is modified; it does neither. Runtime and hardware guidance are strong, but an agent would still not know if the result is a new file, a job handle, or an in-place change, nor any constraint on `height`.

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 0%, so the description must carry parameter meaning. It does well for `method`, naming both accepted values 'simple' and 'ltx' (there is no enum in the schema), and explains what `height` means for the simple path. However `video` is never described, and it is unclear whether `height` is honored for the LTX path, which is hardcoded to 1080p.

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 states a concrete operation — making a video bigger by either resizing to a target height with sharpening, or re-rendering via the LTX second pass to 1080p. The verb is informal ('Bigger video') but the two-method explanation makes the outcome unambiguous. It doesn't differentiate itself from sibling tools explicitly, keeping it just short of a 5.

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

Usage Guidelines4/5

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

It gives clear decision guidance by framing the method tradeoff: 'simple' takes seconds and works on any video, while 'ltx' takes 30-50 min on a 4 GB GPU but produces real detail. That is genuine when-to-use context for the main branch in an agent's decision. It stops short of stating any limitation or exclusion (e.g., max height, when not to upscale at all).

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