garment-cad-mcp
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| project_createA | Create a minimal native-authored Garment Project for drafting from scratch. |
| project_importB | Import native .val and optional Tape files without parsing or rewriting them. |
| project_openA | Open an existing Garment Project and return compact current state. |
| project_statusC | Refresh revision, content hash, GUI-dirty state, and project identity. |
| catalog_searchA | Search atomic tools by name/action/description and optionally load matches. |
| resource_readB | Read a project change-set, preview, thumbnail, or content-addressed artifact. |
| command_previewB | Preview one catalog action without requiring a dynamically refreshed tool list. |
| changeset_commitA | Atomically commit one valid preview at its recorded base revision/hash. |
| changeset_discardA | Discard one immutable preview without changing native CAD truth. |
| revision_revertC | Append a reverse revision from native CAD preimages. |
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 10 tools
Most tools target distinct actions (create, import, open, status, search, read, commit, preview, discard, revert). However, project_open and project_status both relate to viewing project state, which could cause minor confusion, though their descriptions clarify that status refreshes state while open returns it.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., project_create, changeset_commit, revision_revert). No mixed conventions or vague verbs; the naming is highly predictable and readable.
The server has 10 tools, which is well within the typical 3-15 range. Each tool serves a distinct purpose in the garment CAD workflow, and the count feels proportionate to the domain without being excessive or thin.
The tool surface covers core project lifecycle (create, import, open, status), changeset management (commit, discard), and revision operations (revert). Minor gaps exist such as no project deletion or listing, but the provided tools cover the primary workflows.