Text2Sch
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALTIUM_EXE | Yes | Path to Altium Designer's X2.EXE | |
| ALTIUM_DBLIB | Yes | Configured DbLib, including locally managed database access | |
| ALTIUM_JOB_ROOT | Yes | Writable ASCII output path without spaces, quotes, parentheses, or pipes | |
| ALTIUM_SEED_SCHDOC | Yes | Blank schematic bootstrap file created by Altium |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| altium_doctorA | Read-only executable, process and desktop-lock diagnostics. Does not prove the scripting engine is responsive. |
| altium_library_queryB | Read the configured DbLib tables or component records and resolve existing symbol/footprint files. No database writes. Use ALTIUM_DBLIB or supply library. Part-number match supports SQL LIKE wildcards. |
| altium_library_validateC | Validate a DbLib-based circuit and resolve paths using ALTIUM_DBLIB if configured. |
| altium_library_prepareC | Prepare a DbLib-based circuit and native script without launching Altium. |
| altium_library_buildB | Create a new single-sheet, flat or hierarchical project using resolved DbLib records, compare compiled nets, and verify saved supplier parameters and footprint links. Does not verify ERC or native 3D rendering. |
| altium_validateB | Validate a single-sheet, flat or hierarchical circuit specification without opening Altium. |
| altium_prepareC | Write isolated script files and a specification SVG preview. Does not execute Altium. |
| altium_buildA | Create a NEW isolated Altium project, save/reopen/compile it and compare actual pin networks. Requires licensed local Altium. No UI automation. Not a hardware-design/ERC signoff. |
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 8 tools
The set has three near-parallel pairs: validate, prepare, and build each have both a library-based and a non-library variant. Descriptions explain the DbLib distinction, but an agent could still choose incorrectly when the project context is unclear.
All tools use the altium_ prefix and snake_case action names, with library variants adding a clear library_ segment. The pattern is predictable, though the optional resource segment makes it slightly less uniform than a strict verb_noun scheme.
Eight tools is well-scoped for a Text2Sch Altium workflow. Each tool maps to a distinct stage or diagnostic purpose, with no excessive surface.
The surface covers diagnostics, library querying, validation, preparation, and project build, forming a plausible end-to-end workflow. It lacks explicit update/delete or modification operations for existing projects, but those may be intentionally out of scope for a new-project generator.