schematic-architect
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| palettesC | The palettes, by tier, with the block each role builds as. |
| new_designB | Starts an empty design named design (lowercase letters, digits, _ . -; it becomes the blueprint id) with a palette. |
| list_designsB | The designs open in this session, with their palette, size and block count. |
| open_schematicB | Opens a .litematic file as a design to change, its blocks as they are (no roles). |
| set_paletteC | Builds the design's roles from another palette, such as a late-game one; literal blocks stay as they are. |
| set_blockC | Puts one block (a role, a block state, or air). |
| boxB | Fills a box between two corners: mode solid, shell (six faces, hollow inside), walls (four sides, no floor or roof) or frame (the twelve edges). |
| lineC | A one-block line between two points, diagonal too. |
| cylinderB | A cylinder whose first end is centred on x, y, z, running length blocks along +axis (y: a tower, x or z: a tunnel or arch). hollow leaves a tube open at both ends. |
| sphereB | A ball centred on x, y, z. half "top" keeps the upper half (a dome), "bottom" the lower (a bowl). |
| pyramidB | A stepped pyramid on the rectangle x1..x2, z1..z2 starting at height y, one smaller on every side each layer up. Also good for a stepped roof. |
| clearA | Removes every block in a box (doors, windows, hollowing out). |
| replaceC | Swaps every old block or role for new; a block name without state matches all its states. |
| copyB | Copies the blocks of a box dx, dy, dz on (repeat a window, a pillar, a wing), mirrored ("x" or "z") and turned a quarter clockwise (seen from above) turns times within the box. Facing and axis states turn with them. |
| symmetrizeA | Makes the design symmetric across a plane: the low side (smaller x or z) is mirrored onto the high side. center is the plane's x or z; the middle of the design by default. |
| undoC | Takes back the last change (up to 20). |
| materialsC | What the design takes to build: blocks with counts, stacks and tier, and the highest tier it needs. |
| previewB | A picture of the design: "all" (isometric beside top, front and side), "iso", "top", "front" (from the south), "side" (from the east), or "layer" with y (one height, from above, y counted from the bottom of the design). Colours are guessed from block names; glass is see-through. |
| layerB | One height of the design as text, from above (north up, x to the right), y counted from the bottom; a letter a block, "." air. For checking exact positions. |
| exportB | Writes the design as data//blueprint/.litematic in a data pack folder, such as /datapacks/architect, making the pack's pack.mcmeta if it has none. After /reload in game it is blueprint :: pick it with the Blueprint item, and bots build it with build(":", at). A path ending in .litematic writes just that file instead. |
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 20 tools
Most tools target a clearly distinct resource or operation: the five shape primitives (box, line, cylinder, sphere, pyramid), the block-level edits (set_block, clear, replace), and the design lifecycle tools are easy to tell apart. The only mild overlaps are box vs clear vs replace (all act on a box region) and copy vs symmetrize (both mirror geometry), but their descriptions spell out the differences well enough for an agent to choose correctly.
There is a rough logic (shape primitives are bare nouns, design management uses verb_noun like new_design, list_designs, set_palette, set_block), but listing/inspection tools mix conventions: list_designs uses a verb while palettes and materials are bare nouns. It stays readable, but the pattern is not predictable enough to guess a tool name cold.
At 20 tools the set is on the heavy side, but nearly every tool maps to a distinct capability of a schematic editor (five shapes, three block edits, palette handling, four inspection/preview tools, export, undo). Nothing looks like filler, though a few could plausibly be folded together (e.g. layer into preview).
The surface covers the full build loop: create/open/list designs, assign palettes, place and modify geometry, inspect via materials/preview/layer, and export to a datapack. Minor gaps remain: no way to close or delete a design, no rename, no single-block query at a coordinate, and undo has no redo, but agents can work around all of these.