mcp-spatial-critic
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_SPATIAL_CRITIC_PRESETS | No | Override where `list_presets` looks for parametric presets. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_stlA | Audit a STL mesh for watertightness/manifoldness, build-plate grounding, disconnected shells, inverted normals and thin features. |
| generate_reference_boxC | Write a known-watertight reference box and audit it. |
| list_presetsA | List the bundled parametric CAD presets (OpenSCAD / generator). |
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 3 tools
Each tool has a clearly distinct purpose: auditing an existing STL, generating and auditing a reference box, and listing presets. The generate_reference_box tool's inclusion of an audit step does not blur its boundary because it is explicitly a fixture-creation operation.
All three names follow a consistent snake_case verb_noun pattern: audit_stl, generate_reference_box, list_presets. The convention is predictable and readable.
Three tools is on the low end but fits the focused purpose of an STL audit critic. Each tool earns its place, though the surface is somewhat thin for anything beyond basic auditing.
The core audit operation is covered, but the surface has notable dead ends: presets can be listed but not run or inspected, and there is no repair or re-audit workflow for failed meshes. Agents can work around this for simple audits but will hit gaps in a full CAD validation lifecycle.