Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Fix a video beat

fix_beat

Re-render one 1.5-8s window of an existing rendered video and splice it back into the video track only, keeping the rest and all audio unchanged. Repair one broken shot without a full re-render.

Instructions

Surgically re-render ONE time window (1.5-8s) of an existing rendered video and splice it back on the VIDEO TRACK ONLY — the rest of the video and ALL audio stay byte-identical. Use when one beat/shot is broken ('the shot at 8 seconds glitches') and a full re-render would waste the parts that worked; bills only the replacement clip's seconds (~1/3 of a full render). Do NOT pick a window covering spoken dialogue (a video-only splice under speech breaks lip-sync) — pass speechWindows to enforce this.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNotrue = return the exact credits this fix reserves and render nothing
promptYeswhat the replacement footage should show — describe the shot, matching the master's style
refImageNooptional product/style anchor image URL
videoUrlYesthe served URL of the master video to fix
endSecondsYeswindow end in seconds (window 1.5-8s)
startSecondsYeswindow start in seconds
speechWindowsNo[[start,end],...] windows with spoken lines — the fix window must not overlap these

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.320
    • addedInput schema / properties / dryRun
      Added value: +{
+  "description": "true = return the exact credits this fix reserves and render nothing",
+  "type": "boolean"
+}
  2. 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
  3. Addedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: billing model ('bills only the replacement clip's seconds (~1/3 of a full render)'), preservation guarantee ('the rest of the video and ALL audio stay byte-identical'), and the harm mode of a bad window ('a video-only splice under speech breaks lip-sync'). Annotations only declare non-readonly/non-idempotent/open-world; the description carries the real behavioral burden.

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?

Dense but front-loaded and every clause earns its place: purpose first, then routing rationale, then the dialogue warning. Slightly packed into one long flow, but no wasted sentences.

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?

For a mutating, non-idempotent, open-world tool with no output schema and 7 params, the description covers cost, side effects, scope limits, and the critical failure mode. Nothing an agent needs to call it correctly 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 coverage is 100%, so baseline is 3, but the description adds meaning beyond schema: the 1.5-8s window constraint, what dryRun reserves (exact credits), and the lip-sync rationale that makes speechWindows a correctness requirement rather than a hint. Adds genuine value over the field descriptions.

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+resource+scope: 'Surgically re-render ONE time window (1.5-8s) of an existing rendered video and splice it back on the VIDEO TRACK ONLY.' The scope (single window, video track only, audio untouched) distinguishes it sharply from full-render siblings like render_ad or edit_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?

Gives an explicit when ('one beat/shot is broken') including an example utterance, explains the alternative it displaces ('a full re-render would waste the parts that worked'), and adds an explicit exclusion ('Do NOT pick a window covering spoken dialogue') with a mitigation ('pass speechWindows').

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