Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SCAD_PRESETS_FILENoOptional path to a read-only JSON file defining presets and default presets for models.
SCAD_ARTIFACTS_DIRNoDirectory where generated artifacts are stored. Run from the project directory so the default artifacts/ directory is predictable, or set this explicitly.
SCAD_MCP_API_KEY_FILENoPath to the owner-only file containing the API key for the HTTP runtime. The file must be owned by UID 568 and contain 32–4096 printable ASCII bytes with no whitespace./run/secrets/scad-mcp-api-key
SCAD_MCP_GATEWAY_KEY_FILENoOptional path to a second independently revocable API key file. Both keys grant access to every tool; equal, missing, or unsafe keys cause startup failure.

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
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_modelsA

List available parametric models with parameter schemas, presets, resolved defaults and licenses.

generateB

Render STL and optionally PNG preview in artifacts dir. Preset defaults apply unless preset is given; per-call params override the preset. Unknown presets or params are rejected. Unknown licenses require allow_unknown_license=True. Returns artifact filename and STL metrics.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 2 tools

Disambiguation5/5

The two tools occupy clearly separate phases: list_models is pure discovery of schemas/presets/licenses, while generate performs rendering and returns artifacts. There is no plausible way to confuse them, and the descriptions reinforce the discovery-then-generate workflow.

Naming Consistency4/5

list_models follows a clear verb_noun pattern, but generate is a bare verb with no object, so the convention is not uniform. It is still readable and predictable given only two tools.

Tool Count3/5

Two tools is thin for a parametric CAD surface; discovery and rendering are covered, but anything beyond that (inspection, validation, artifact handling) has no entry point. The scope is defensible but feels minimal rather than well-scoped.

Completeness3/5

The core lifecycle (see what models exist, render one) is covered, but there is no get_model for drilling into a single schema, no explicit parameter/preset validation call, and no artifact listing or cleanup. Agents can work around this by reading list_models output, but the surface has notable gaps.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues