Construct
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hologram_templateC | Return a synthetic starter tessera-hologram sheet for a kind. |
| hologram_validateC | Validate a tessera-hologram sheet; returns error list. |
| hologram_compileB | Compile a tessera-hologram sheet into tessera-geometry. |
| construct_diagnoseA | Check a v2 scene or parameter document (contract construct/0.2): every problem with a JSON path, a code and a fix hint, plus repair_text to send back to the model that wrote it. Give |
| construct_params_templateB | A parameter document to fill in for an archetype (case, book, object, vessel) and variant: the simple path for models that struggle with full scenes. Without arguments: every archetype. |
| construct_expand_paramsC | The full v2 scene a valid parameter document builds (or its diagnostics when it is not valid). |
| construct_compileA | Compile a valid v2 scene or parameter document into construct-geometry v2 (or return its diagnostics). Artwork bytes are never read: slots carry asset ids and hashes only. |
| construct_exportB | A 3D model of a valid v2 scene or parameter document: glTF 2.0 (base64 .glb: named parts, materials by role, the open and idle animations, each vertex's build phase as _PHASE) or OBJ text with its MTL. Opens in Blender, Godot, Unreal, Unity (glTFast) and three.js. |
| construct_printA | One watertight body of a valid v2 scene or parameter document, to 3D print: 3MF (default) or binary STL, base64, in millimetres, Z up, on the bed; with the checks (watertight, separate pieces, fits the bed, overhangs that need supports, what was thickened) and the scale. |
| construct_netlogo_instrumentA | A NetLogo 7 model (.nlogox text) that records its run for Construct: the recorder included, set up after setup's reset-ticks and recording after go's tick (or the model's own buttons; a model that never ticks records by steps). Returns the model, a headless BehaviorSpace experiment and the recorder (construct.nls) to save beside it; run it in NetLogo, then draw run.jsonl with construct_netlogo_draw. NetLogo models in the library keep their own licence. |
| construct_netlogo_drawB | A construct of a recorded NetLogo run (the JSON Lines a run writes), computed from the data alone, with its legend, how-to-read lines, replay clock and counts, and a data lock. Views: space-time (moving agents), network-time (spreading on a network; give state), phase (two reporters in a cycle), field (spreading over patches), pulse (turtles switching a state on and off: how many at once, tick by tick), auto (the one the data suits). Moving agents and pulses are drawn over the window where their order formed when it forms early (window: auto, whole, or a tick). Optional: an art-direction layer (art: views, labels, milestones; never the data), solid (spheres, tubes, a surface, for a 3D model) and materials (the run's own colours, for construct_export). Compile or export the scene with the other tools. |
| construct_limitsB | The limits of a mode (fast, masterpiece, timeboxed, unbounded) or tier (wall clock, check and review rounds, research counts) with any overrides applied, for the host to enforce: aim for genuinely good, stop at the first limit. Overrides can raise a limit, never remove it. Also reads 'mode:'/'tier:'/'research:' from a request. |
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 12 tools
The two families are conceptually separate (hologram/legacy vs construct/v2), but within them the boundaries blur: hologram_validate vs construct_diagnose vs hologram_compile vs construct_compile all sound like 'check or compile a document', and construct_compile explicitly also returns diagnostics. Dense jargon (tessera-hologram, v2 scene, parameter document, construct-geometry v2) forces the agent to infer which artifact each tool accepts, which invites misselection.
Almost every name is prefix_verb or prefix_verb_noun (hologram_validate, construct_compile, construct_diagnose, construct_export, construct_print, construct_netlogo_draw). The deviations are the two *_template noun-final names (hologram_template, construct_params_template) and the compound verbs expand_params/netlogo_instrument, but the pattern remains readable.
Twelve tools is well within the comfortable range and each maps to a distinct pipeline stage (template, validate/diagnose, compile, export, print, netlogo instrument/draw, limits). No tool looks like filler.
The surface covers a coherent lifecycle: scaffold a document, check it, compile it, then export to glTF/OBJ or printable 3MF/STL, plus a NetLogo data-visualization branch and a limits query. Gaps are minor — the hologram family has no export/print counterpart, and there's no tool to enumerate archetypes/variants or preview a construct other than via export.