Skip to main content
Glama

lipsync

Aligns a real person's lip movements to a supplied voice track for talking-head video edits. Requires a GPU with 8 GB or more.

Instructions

Moves a real human face's lips to a voice (LatentSync). Needs a graphics card with 8 GB or more.

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

Input Schema

NameRequiredDescriptionDefault
audioYes
videoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world operation, so the safety profile is covered. The description adds the GPU memory requirement, which affects whether the call will succeed. It says nothing about output artifacts (presumably a new rendered video), processing time, or failure modes.

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 short sentences, front-loaded with the core action before the hardware requirement. Nothing is padded, though the wording is so terse that useful detail is absent rather than trimmed.

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 no annotations describing results, the description carries the burden of telling the agent what it gets back (a rendered video file, its naming, duration behavior). It covers feasibility (GPU) and intent but not outcome, which is a meaningful gap for a render job.

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 description coverage is 0%, so both 'video' and 'audio' strings are undocumented in the schema. The description implies the semantic roles — video supplies the face, audio supplies the driving voice — which is meaningful beyond bare string types. It still omits accepted formats, path vs. URL conventions, and whether the audio may be longer than the video.

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 verb and resource: moving a real human face's lips to a voice track, and names the underlying technique (LatentSync). An agent can distinguish this from siblings like add_voice or add_captions, though the description doesn't explicitly say how it differs from them.

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?

A hardware precondition is given ('needs a graphics card with 8 GB or more'), which is genuinely useful gating information. However, there is no guidance on when to choose this tool versus audio/text-oriented siblings, and no statement of what inputs are acceptable.

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