Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CHROME_PATHNoAny Chrome, Chromium or Edgeauto-detected
FFMPEG_PATHNoUse your own ffmpegbundled
ELEVEN_FORMATNomp3_44100_192 on Creator plans and upmp3_44100_128
BLOCK_STUDIO_HOMENoEpisodes, takes, render jobs and the audio cache~/3dBlockStudio
ELEVENLABS_API_KEYNoVoice, sound effects, music. Or put the key in ~/.config/elevenlabs.key. Optional: without it, renders are silent drafts.

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
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
studio_infoA

Check the setup: studio folder, Chrome, ffmpeg, whether an ElevenLabs key is configured, engines and series formats.

list_formatsB

The series formats this studio makes (engine, target length, rules).

get_house_rulesA

The house rules every crew role follows: the look, copyright, format, working rules. Read before writing anything.

get_crew_briefB

Get one film-crew role's brief so you can act as that role. Roles: casting-director, cinematographer, colorist, director, editor, gaffer, producer, production-designer, script-supervisor, sound-engineer, writer.

get_engine_guideB

How an engine works and its API: ps1 (low-poly 3D), woodcut (living broadsheet), timeline (shared helpers: at/st/en word timing, easing).

new_episodeC

Create an episode folder from a series template (a working placeholder scene that renders as-is).

list_episodesB

Your episodes, plus the built-in examples you can read.

read_episodeA

Read every file of an episode or example (spec.js, scene.js, notes). Use the examples as reference builds.

read_fileC

Read one file of an episode.

write_fileA

Write spec.js (script, voice, music, sound cues), scene.js (the three.js scene) or a crew note (.md/.json). JS is syntax-checked and the spec validated before saving; the old version is kept in .history.

list_propsA

Browse the low-poly prop library (people, furniture, places, vehicles). Without module: the modules and their builders. With module: its full usage guide.

preview_propB

Render one prop builder from 4 angles next to a 1.75 m reference person, and return the image.

list_voicesA

The ElevenLabs voices on your account (needs a key).

voice_linesA

Voice every line of an episode's script with ElevenLabs (cached by hash: unchanged lines cost nothing) and generate its sound effects. Returns each line's length and the episode's approximate length.

render_stillsA

Start a contact-sheet render (30 evenly spaced frames, or chosen times) for a quick look before a full take. Poll job_status; the finished job returns the image.

render_takeA

Start a full render of the next numbered take: frames, voice, sound effects, music, loudness-normalized mix, thumbnail, contact sheet and QC. Takes minutes; poll job_status.

job_statusA

Progress of a render job. A finished stills job returns its contact sheet; a finished take returns its file, thumbnail and QC.

list_jobsB

All render jobs since the server started.

list_takesC

The numbered takes of an episode.

qc_takeA

Check a take: length against the series target, loudness (-14 LUFS), the loop seam (first vs last frame), and the copyright checklist.

pick_takeA

Mark a take as the FINAL (only when the user chooses it). Copies it to " - FINAL.mp4" and refreshes the thumbnail.

open_takeB

Open a take in the computer's video player so the user can watch it.

post_kitC

Write the post kit next to the takes: caption, up to 5 hashtags, song note, posting time. The answer of a guessing format is kept out of the caption.

Prompts

Interactive templates invoked by user choice

NameDescription
casting-directorBuilds the cast sheet from the cast library (body, face, hair, wardrobe, props in hand) to match the film's era and characters, and makes lookbook sheets for the showrunner (the user).
cinematographerWrites the shot list in film language through the cinema camera (body, lens, f-stop, move, focus, size) and exposes for the gaffer's light.
coloristGrades the raw plates after every shoot: picks a power grade for the film's real look, matches every shot, adds the film layer (halation, grain, print curve) and checks scopes. Can be rerun any time to regrade.
directorRuns the crew for one episode. Writes the treatment, blocks the scenes, reviews every stage (dailies) and signs off or sends work back with notes.
editorCuts the raw shot clips to the narration into an edit list, holding the TikTok playbook pacing and the loop seam.
gafferLights every scene with the lighting engine: the sun and sky by time and place, film fixtures, practicals, flicker and haze, measured in stops for the cinematographer.
producerRuns the render queue on the render machine, numbers the takes, opens each take on the user's screen, backs up to the backup drive, writes the post kit, and logs render time and cost per episode.
production-designerPicks and dresses the sets from the sets library, places hero props and the hidden clue, sets time of day and weather, and builds any new library piece in the PS1 style.
script-supervisorRuns every pre-shoot check (clipping, cameras in walls, the 180-degree line, continuity of props, blood and costume) and blocks the shoot until they pass.
sound-engineerDesigns and mixes the sound against the locked cut: narration on top, foley tied to the animation, ambience per set, music cues and the TikTok song slot, delivered at -14 LUFS.
writerResearches the film and writes the narration script, clue ladder and hidden clue into spec.js, without ever naming the movie.
make_episodeMake a whole short with the crew, from idea to finished take.

Resources

Contextual data attached and managed by the client

NameDescription
house-rules
phoenix-lights-1997/spec.js
phoenix-lights-1997/scene.js
the-cursed-tape-ps1/spec.js
the-cursed-tape-ps1/scene.js

TDQS

B3.2/5.0

Scored across 23 tools

Disambiguation4/5

Most tools have clearly distinct purposes: setup (studio_info, list_formats, get_house_rules), reading (read_episode vs read_file, clearly scoped), rendering (render_stills vs render_take, distinguished by stills/contact sheet vs full take), and delivery (pick_take, open_take, post_kit). A few pairs could trip an agent: list_takes vs list_jobs (takes vs render jobs), and voice_lines bundles both voice and sound-effect generation. The descriptions help resolve these, so boundaries are mostly clear.

Naming Consistency4/5

Nearly all tools follow a verb_noun or noun_info pattern: list_formats, get_crew_brief, render_take, qc_take, pick_take, open_take. Minor deviations: 'new_episode' instead of create_episode, and 'job_status' as a noun_noun form breaking the verb pattern. All snake_case is consistent, so it reads predictably.

Tool Count4/5

23 tools is at the upper edge but justified by a genuinely multi-stage pipeline: setup, rules/briefs, episode authoring, props, voicing, rendering, QC, and posting. No tool looks redundant enough to remove, though it is slightly heavy.

Completeness4/5

The full lifecycle is covered: create/read/write episodes, inspect props and voices, voice lines, render stills and takes, poll jobs, QC, pick final, open, and post kit. Minor gaps: no delete/cleanup for episodes or takes, and no explicit way to update episode metadata beyond rewriting spec/scene. These are workaroundable.

Maintenance

ActivityMaintained
ResponsivenessOutdated data