Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_projectC

Start a new Timeline-as-Data project.

load_projectC

Load a project from JSON.

save_projectC

Save the project to JSON.

readB

Read the timeline at a zoom level (the agent inspects its work).

renderC

Compile the timeline to video (deterministic) and optionally QC it.

qcD

Run deterministic QC on a rendered file.

ingest_assetC

Ingest a media file: detect scenes, transcribe, analyze, index.

build_narrativeC

Build cross-asset narrative index from all ingested assets.

search_indexC

Search the semantic media index by text.

remove_silencesC

Remove silent portions from clips on a track.

reframe_toC

Reframe a video asset for a different aspect ratio.

sync_cuts_to_beatC

Snap clip transitions to the nearest beat in the audio track.

generate_captionsD

Generate captions from the transcript.

auto_duckingC

Automatically duck music volume when voice is present.

assemble_from_planC

Assemble a cut from a structured edit plan (JSON string).

make_shortC

Create a short clip from source material matching a topic.

vlm_reviewC

Run VLM semantic review on a rendered video.

render_proxyC

Render a fast low-resolution proxy for review.

run_agent_swarmC

Run the multi-agent swarm to edit a video from a brief.

export_otioA

Export the project as an OpenTimelineIO (.otio) file.

import_otioC

Import an OpenTimelineIO file into the current project.

render_farmC

Render using the distributed render farm.

render_farm_dry_runA

Show what the render farm would do without rendering.

add_assetD

Register a source asset.

add_trackD

Add a track.

add_clipC

Place a slice of an asset on a track (returns a diff).

trimC

Adjust a clip's source in/out.

moveC

Move a clip on its track.

splitC

Split a clip at timeline time t.

ripple_deleteA

Delete a clip and close the gap.

set_speedC

Set clip playback speed.

set_volumeC

Set clip volume.

add_transitionB

Add a fade in/out to a clip edge.

add_text_layerC

Add a burned-in caption/title.

add_audioC

Add an audio clip (music bed / VO).

checkpointD

Snapshot current state.

undoC

Revert to the last checkpoint.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.6/5.0

Scored across 37 tools

Disambiguation5/5

Each tool targets a distinct operation: rendering has four variants (direct, proxy, farm, dry-run) but descriptions clarify the differences. Editing operations are specific (add_clip, trim, move, split, ripple_delete, set_speed, set_volume) with no overlap. Semantic tools (build_narrative, search_index, vlm_review) are clearly different.

Naming Consistency5/5

All tool names use lowercase with underscores, consistent verb-first pattern (create_project, ripple_delete, sync_cuts_to_beat). Abbreviation 'qc' is acceptable. Conventions are uniform across the set.

Tool Count2/5

With 37 tools, the server exceeds the 25-tool threshold for 'too many' per the rubric. However, the video editing domain requires many operations, but the count is still high and may overwhelm agents.

Completeness5/5

The tool surface covers the full lifecycle: project management, asset ingestion, editing, audio, effects, rendering, QC, export/import, and even an agent swarm. No obvious gaps such as project deletion or asset removal, but those are minor.

Maintenance

ActivityInactive
ResponsivenessNo issues