Model Lab
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MODELLAB_OUT | No | The only folder Model Lab writes to. Defaults to `~/.modellab`. | |
| MODELLAB_BLENDER | No | Blender's executable. Leave it out when Blender is on the PATH or in its usual install folder. | |
| MODELLAB_IDLE_OK | No | With `MODELLAB_WAIT_FOR`: parts of a command line that mark a long-lived worker (default `poselab_mcp`). Such a worker counts only while it is busy. | |
| MODELLAB_WAIT_FOR | No | Optional process names that hold the machine, such as `UnrealEditor.exe,blender.exe`. A build refuses to start while one runs. Off by default. |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_platformsB | The gun families Model Lab can draw, with their parameter names. |
| describe_paramsC | A platform's parameters (type, range or choices, unit, meaning) and the sources its real numbers come from. |
| list_presetsB | The ready guns (M4A1, M16A2, AR15, M4A1_Kitted, AR15_Optic): their parameters and the published lengths each build is checked against. |
| list_attachmentsA | The attachments a build can mount on the rails and M-LOK slots (optics, backup sights, the carry handle, a vertical grip, a light): what each is, the rails it fits, its states and moving parts. Pass them to build_gun as params.attachments. |
| list_referencesC | The real-gun photos compare_to_reference measures against: each photo's source, licence, scale and the build that matches it. |
| build_gunA | Builds a gun in Blender (15 to 30 s): the rig FBX, the hand magazine FBX, one FBX an attachment, the .blend (with the cycle as an action), facts.json and a sheet of labelled dev views; with motion, GIFs of the cycle. Returns the checks that failed (none when all_pass), the size and the files. |
| build_gun_clipsB | The gun's own clips on a build's rig, from real beats and timings at 60 frames a second: each measured (parts on their axes, the bolt's stroke, the cover open before the carrier, the magazine out of the well and seated, the bolt held on its catch), exported alone as FBX (A__.fbx) and shown as a GIF. |
| compare_to_referenceA | The real-gun check: draws the build's side outline at the reference photo's scale and alignment, measures both outlines column by column, and returns the stretches that differ by more than 0.4 cm, each with the parts there and its zone (the gun, or an attachment over the rail), and an overlay picture (the model in red over the photo). |
| list_buildsA | The latest builds, newest first: name, whether every check passed, size. |
| read_buildC | A build's facts: parameters, marks, moving parts, rails, attachments, the parts table, every check, files. |
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 10 tools
Most tools target clearly distinct resources/actions: list_platforms, list_presets, list_attachments, list_references, list_builds each return different data, and build_gun vs build_gun_clips vs compare_to_reference are distinct operations. The only mild overlap is between list_platforms (parameter names) and describe_params (parameter details), and list_presets also surfaces parameters, so boundaries are mostly but not perfectly crisp.
All ten tools follow a consistent snake_case verb_noun pattern (list_*, describe_params, build_gun, build_gun_clips, compare_to_reference, read_build). Verbs are used coherently across the set with no style mixing.
Ten tools is well-scoped for a gun build-and-verify pipeline: discovery (platforms, params, presets, attachments, references), generation (build_gun, build_gun_clips), verification (compare_to_reference), and inspection (list_builds, read_build). Each tool earns its place.
The surface covers the full build workflow: parameter discovery, building, animation clips, real-reference verification, and build inspection. Minor gaps exist, such as no tool to delete/manage builds or to list/inspect individual clips, but these are workable.