Kodecz
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| renderA | Render a Kodecz video folder to MP4 (GPU with NVENC when there is one, CPU with x264 when not). Returns the render's JSON result line. Run |
| previewA | Draw some frames of a Kodecz video as lossless PNGs (the same pixels as the render, one to two seconds) and return them as images. Use it to look at what you wrote instead of guessing. |
| checkA | Run Kodecz's automatic checks on every frame without rendering: text over the presenter's face, captions on one line, the safe area of a declared social destination, contrast over the real background, zoom timing. Returns the JSON result, each problem with its frame, and pictures of the worst frames. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly separate role: check validates rules, preview samples frames as images, render produces the final MP4. The descriptions explicitly encode the workflow order (`check` first), so an agent can't mistake one for another.
All three are single, lowercase verbs (render, preview, check) with no casing or style deviation. The pattern is predictable and readable.
Three tools is a tight, well-scoped surface for a render-and-verify pipeline, with no redundancy. It sits at the low end, with no tool for inspecting or listing video folders, which leaves the set slightly thin.
The validate → preview → render lifecycle is covered, including failure reporting with offending frames, so the core loop has no dead ends. Minor gaps exist: nothing to discover or initialize a Kodecz folder and nothing to clean up output artifacts.