mcp-server-autocad-lisp-helper
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 |
|---|---|
| analyze_lisp_syntaxA | Checks AutoLISP code for balanced parentheses, quotation marks, comments, and structural syntax errors with exact line and column numbers. |
| extract_lisp_functionsA | Extracts function definitions (defun C:...), argument lists, and localized variables from AutoLISP code. |
| check_missing_cleanupsB | Identifies unhandled local variables (assigned via setq but not declared after '/') and unmodified system variables to prevent AutoCAD state leakage. |
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 targets a clearly distinct analysis concern: structural syntax validation, function/variable extraction, and cleanup/state-leakage checking. Although all three operate on AutoLISP source statically, the descriptions draw sharp boundaries so an agent can select correctly with no overlap.
All three names follow a strict verb_noun snake_case pattern (analyze_..., extract_..., check_...). The convention is uniform and self-describing, with no mixed casing or verb styles.
Three focused tools is at the low end of the typical 3-15 range but each earns its place for a narrow lint-style helper. It is not bloated, though the surface feels slightly thin for a full AutoLISP assistance workflow.
The set covers the core static-analysis lifecycle for AutoLISP: syntax validation, symbol/function extraction, and cleanup-state auditing. Minor gaps exist around remediation (auto-fix/format) or deeper cross-reference/usage analysis, but agents can work around these.