Skip to main content
Glama
hoklims

material-workbench

by hoklims

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tasks
{
  "list": {},
  "cancel": {},
  "requests": {
    "tools": {
      "call": {}
    },
    "prompts": {
      "get": {}
    },
    "resources": {
      "read": {}
    }
  }
}
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
initializeC

Handshake. Returns sidecar version + cache_root + capabilities.

shutdownC

Returns {ok: true}. Client-side disconnect is the actual close.

workspace_setA

Change workspace_root at runtime. Pass null to clear.

archetype_listA

List all registered archetypes with their params and modifiers.

recipe_readB

Read a recipe JSON file. scope must be 'workspace' or 'app_data'.

recipe_writeC

Write a recipe to disk after normalization. Returns render_hash.

recipe_normalizeB

Normalize a recipe (clamp params, derive seeds, recompute hash).

recipe_validateC

Validate a recipe. Returns {valid: bool, errors: list}.

recipe_mutateC

Apply patches [{param_path, value}], re-normalize, return new hash.

render_runC

Render a recipe. Returns manifest + render_source enum.

render_cancelA

Cancel a render request. Idempotent.

cache_lookupB

Look up a cached manifest by render_hash.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 12 tools

Disambiguation5/5

Each tool targets a distinct action and resource: archetypes, cache, recipes (multiple operations), rendering, server control, and workspace. No two tools overlap significantly in purpose.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern using lowercase snake_case (e.g., recipe_read, render_run). No deviations or mixed conventions.

Tool Count5/5

12 tools cover the domain comprehensively without unnecessary duplication. The number feels appropriate for a material/workbench server.

Completeness4/5

Core workflows (read, write, normalize, validate, mutate, render) are present, but there is no explicit delete recipe tool or a way to list all recipes. Minor gaps that agents might work around.

Maintenance

ActivityInactive
ResponsivenessNo issues