Skip to main content
Glama

compose

Trims, syncs, muxes, and captions demo footage into output/final-demo.mp4 with timed SRT/VTT files. Returns a jobId immediately for status polling and rejects concurrent jobs.

Instructions

Trim, sync, mux and caption into output/final-demo.mp4 (+ final-demo.srt/.vtt timed to it). Returns a jobId immediately — poll job_status. Rejects if another job is running.

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": {
      "dir": "<dir>"
    },
    "name": "compose"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirYesdemo project directory — pass an absolute path
gifNoalso export output/final-demo.gif
langNorender a language variant from scene.narrations[<code>] over the shared take (artifacts namespaced: audio/<code>/, captions.<code>.*, output/final-demo.<code>.mp4). Omit for the default single-language render.
paramsNostoryboard template params (name → value); each must be declared in the storyboard's params block. Substitutes {{name}} across all stages.

Output Schema

NameRequiredDescriptionDefault
kindYes
jobIdYes
statusYes
demoDirYesresolved absolute demo directory
logFileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.20.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / params / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv0.9.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the disclosure burden and does well: it reveals the asynchronous contract (immediate jobId, poll job_status) and a concurrency guard that rejects concurrent jobs. It stops short of saying whether existing output/final-demo.* files are overwritten or whether partial artifacts survive a failure, which matters for a multi-stage render.

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 short sentences: what it produces, the async contract, and the rejection condition. Outputs are front-loaded and every sentence carries distinct information with no repetition of the schema.

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 four-parameter, nested-object, asynchronous composition tool with an output schema, the description covers outputs, the polling pattern, and the concurrency constraint. It omits overwrite/reversibility semantics and required prior stages, which leaves a small but real gap for a tool that writes files.

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 100%, so dir, gif, lang, and params are already documented in the schema, including the lang artifact namespacing and the {{name}} substitution rule. The description adds no parameter-level information beyond that, so the baseline 3 applies.

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 names concrete operations (trim, sync, mux, caption) and the exact artifacts produced (output/final-demo.mp4 plus .srt/.vtt), so the agent knows precisely what the tool does. It does not contrast itself with the sibling 'render' or 'captions' tools, so the agent must infer the boundary between compose and those stages.

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?

It gives real operational guidance: the call is async, poll job_status, and the call will be rejected while another job runs. However, it never states when to choose compose over siblings like render, captions, or gif, nor what preconditions (validated storyboard, recorded take, generated voice) must already hold.

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