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.

List TQS buildings under a root folder. A building is a subfolder containing EDIFICIO.DAT. Defaults to the TQS_ROOT environment variable.

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.

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.

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.

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.

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.

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 result to return structured data; stdout is captured and returned too. This can create, modify and delete project files.

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.