tqs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TQS_ROOT | No | Root of the building tree | none |
| TQS_PYTHON | No | Interpreter with the TQS package installed | the server's own interpreter |
| TQS_MCP_TIMEOUT | No | Default subprocess timeout in seconds | 120 |
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 |
|---|---|
| tqs_statusA | Check whether the TQS Python Interface is reachable. Reports the interpreter in use, which TQS modules import, and the TQS programs/support/user folders. Run this first when TQS tools misbehave. |
| tqs_list_buildingsA | List TQS buildings under a root folder. A building is a subfolder containing EDIFICIO.DAT. Defaults to the TQS_ROOT environment variable. |
| tqs_building_readA | Read a TQS building into JSON: project metadata, analysis model, floors, concrete strengths, covers and load cases. Pass a building folder or a path to EDIFICIO.DAT. |
| tqs_building_editA | Change building properties and save. Defaults to dry_run=true, which reports the old and new value of every change without writing. Set dry_run=false to commit; TQS keeps the prior version as EDIFICIO.BAK. |
| tqs_dwg_readA | Read a TQS drawing (.DWG): scale and system metadata, extents, levels, blocks, entity counts, and entities themselves. Filter by entity type, level, or text content — extracting TEXT entities is the usual way to pull rebar callouts and labels out of a drawing. Units are centimeters. |
| tqs_processA | Run TQS Manager processing tasks against a building (TQSExec) — global processing, drawing generation, rebar schedules. This overwrites calculation results and drawings in the building tree, and can run for many minutes. See the tqsexec reference for the task list. |
| tqs_introspectA | Inspect the installed TQS API: list a module's or object's real methods and properties with signatures. Use this whenever you are unsure a name exists — the published docs cover only part of the surface. |
| tqs_run_scriptA | Run Python with the TQS modules importable, in a separate process. The escape hatch for anything the other tools do not cover. Assign to a variable named |
| tqs_referenceA | Bundled offline reference for the TQS Python Interface. Call with no arguments to list topics. Read the relevant topic before writing TQS code with tqs_run_script. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| TQS reference: other-modules | TQS Python Interface reference — other-modules |
| TQS reference: overview | TQS Python Interface reference — overview |
| TQS reference: tqsbuild | TQS Python Interface reference — tqsbuild |
| TQS reference: tqsdwg | TQS Python Interface reference — tqsdwg |
| TQS reference: tqsexec | TQS Python Interface reference — tqsexec |
| TQS reference: tqsgrid | TQS Python Interface reference — tqsgrid |
| TQS reference: tqsutil | TQS Python Interface reference — tqsutil |
TDQS
Scored across 9 tools
Each tool targets a distinct concern: processing, building read/edit/list, DWG read, plus supporting utilities (status, introspect, reference, script). There is no meaningful overlap; even introspect and reference are complementary (live API inspection vs offline docs).
All tools share the 'tqs_' prefix, but the verb/noun order is inconsistent: some are verb-first (tqs_list_buildings, tqs_run_script), others noun-first (tqs_building_read, tqs_dwg_read), and a couple are bare nouns (tqs_status, tqs_reference). Names are still clear and readable, but a uniform pattern would be better.
With 9 tools, the server is well-scoped. It covers the core domain operations (buildings, drawings, processing) alongside essential utilities (status, docs, introspection) without unnecessary bloat.
The surface covers listing, reading, editing buildings, reading DWGs, and running processing tasks. Dedicated create/delete building tools are missing, but tqs_run_script explicitly serves as an escape hatch for creating or deleting project files, mitigating the gap. No DWG editing tool exists, but that seems outside the primary scope.