Skip to main content
Glama

AetherWave Studio

by com.aetherwavestudio.mcp
OverviewDiscussionsAdmin

Upscale video (Atlas / BytePlus)

aetherwave_upscale_video

Upscales a source video. Pass a public videoUrl and a target tier. Two engines: Atlas reaches 1080p and 2k only (7 and 10 cr/s; clips up to 53s at 1080p and 23s at 2k, source <=30fps); BytePlus also reaches 4k and 8k (4/8/16/62 cr/s at 1080p/2k/4k/8k) and is selected automatically for 4k and 8k. IMPORTANT, A TIER IS NOT A DIMENSION. These names are 16:9 standards, so '4k' means the 3840x2160 BOX and the source is fitted inside it, which means the SMALLER dimension wins. A square source at '4k' returns 2160x2160, NOT 3840x3840. Measured. A 3:4 source at Atlas '2k' returned 1664x2216. So never assume a tier lands on an exact pixel target: pick the highest sensible tier, then resize to exact dimensions in ffmpeg. Do NOT escalate to 8k to compensate, it is 62 cr/s to buy reconstruction a free lanczos resize gets you. For reference, Apple Music Album Motion Artwork requires exactly 3840x3840 and 2048x2732, and no tier produces either directly. Returns the upscaled video URL (R2-hosted).

Returns within ~45 s. If the result has state "running" the job is still rendering: poll aetherwave_get_job with the returned taskId and kind every ~10 s. Pass wait:true ONLY if your MCP client permits tool calls longer than 60 s (most do not). Pass async:true to get the taskId back immediately without waiting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNoBlock until the job finishes (up to the tool's full budget, 6-15 minutes). ONLY if your MCP client permits tool calls longer than 60 s; most abandon the call at 60 s and lose the taskId. Default false: return within ~45 s and hand back a taskId if still running.
asyncNoSubmit and return the taskId immediately without polling at all. Then poll aetherwave_get_job(taskId, kind).
videoUrlYesPublic URL of the source video (MP4).
upscaleProviderNoWhich engine. Defaults to Atlas at 1080p/2k. BytePlus is cheaper at both shared tiers and is forced for 4k/8k, which Atlas cannot produce.
targetResolutionNoTarget TIER, not exact dimensions. Defaults to '1080p'. The source is fitted inside a 16:9 box, so the smaller dimension wins: a square at '4k' yields 2160x2160. '4k' and '8k' need BytePlus and route there automatically.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / targetResolution / description
      Previous value: -"Target output resolution. Defaults to '1080p'. '2k' is more expensive and limited to ~23s clips."New value: +"Target TIER, not exact dimensions. Defaults to '1080p'. The source is fitted inside a 16:9 box, so the smaller dimension wins: a square at '4k' yields 2160x2160. '4k' and '8k' need BytePlus and route there automatically."
    • changedInput schema / properties / targetResolution / enum
      Previous value: -[
-  "1080p",
-  "2k"
-]New value: +[
+  "1080p",
+  "2k",
+  "4k",
+  "8k"
+]
    • addedInput schema / properties / upscaleProvider
      Added value: +{
+  "description": "Which engine. Defaults to Atlas at 1080p/2k. BytePlus is cheaper at both shared tiers and is forced for 4k/8k, which Atlas cannot produce.",
+  "enum": [
+    "atlas",
+    "byteplus"
+  ],
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / async
      Added value: +{
+  "description": "Submit and return the taskId immediately without polling at all. Then poll aetherwave_get_job(taskId, kind).",
+  "type": "boolean"
+}
    • addedInput schema / properties / wait
      Added value: +{
+  "description": "Block until the job finishes (up to the tool's full budget, 6-15 minutes). ONLY if your MCP client permits tool calls longer than 60 s; most abandon the call at 60 s and lose the taskId. Default false: return within ~45 s and hand back a taskId if still running.",
+  "type": "boolean"
+}
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare this is a non-readOnly, open-world, non-idempotent, non-destructive mutation, and the description adds real behavioral context beyond that: ~45 s return window, 'running' state polling cadence, R2-hosted output, per-tier credit costs, and automatic engine routing for 4k/8k. This is rich disclosure for a job-submitting 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?

Front-loaded with the core action and required inputs, and every sentence carries actionable content (costs, timing, the box-fit gotcha). It is dense and long, with some repetition of the schema's 4k/8k routing rule and wait-flag guidance, which keeps it short of a 5.

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

Completeness5/5

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

With no output schema, the description correctly explains return values (upscaled video URL, R2-hosted, taskId and state) and the async/polling protocol. Nothing an agent needs to invoke and follow up on this tool is missing.

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 baseline is 3, but the description adds meaning the schema does not: measured examples (a 3:4 source at Atlas '2k' returned 1664x2216), the ffmpeg resize workaround, and the concrete credit costs per tier. It reinforces the 'tier is not a dimension' semantics that the schema states more briefly.

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 ('Upscales a source video'), names the two engines (Atlas/BytePlus) and their tier coverage, and is inherently distinguishable from the sibling aetherwave_upscale_image and aetherwave_reframe_video. An agent can identify the tool without opening the schema.

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?

Gives explicit when/when-not guidance: 'pick the highest sensible tier, then resize to exact dimensions in ffmpeg', 'Do NOT escalate to 8k to compensate', 'Pass wait:true ONLY if your MCP client permits tool calls longer than 60 s', and 'Pass async:true to get the taskId back immediately'. It also names the polling alternative (aetherwave_get_job) and the condition that selects it.

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

All AetherWave Studio toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources