trane-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRANE_ALLOW_SETPOINT_WRITE | No | Set to 'true' to enable setpoint writes (read-only by default). | false |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_buildingsA | List buildings managed by the operator's Trane Tracer SC+ instance. Standard read path for an agent that needs to enumerate the BAS surface. |
| list_equipmentA | List HVAC equipment at a building (AHUs, chillers, boilers, VAV boxes, fan coils, etc.). Used by an agent scoping work for a building. |
| get_equipmentA | Get full metadata for a single equipment unit including current health flags, model, and linked points. |
| read_pointB | Read the current value of a BACnet point on equipment (e.g. supply-air temperature, zone setpoint, damper position). Standard read path for live BAS state. |
| set_setpointA | Write a new setpoint value to equipment. Gated by TRANE_ALLOW_SETPOINT_WRITE=true because writes change real HVAC behavior in real buildings. The MCP refuses unless the operator has explicitly authorized writes. |
| list_alarmsB | List active alarms across the operator's Tracer SC+ deployment. Used by an on-call agent triaging what is unhealthy. |
| list_schedulesB | Inventory operating schedules for buildings + equipment. Used by an agent planning around occupancy or seasonal modes. |
| list_trendsB | Inventory trend logs (historic telemetry). Used by an agent inspecting recent equipment behavior. |
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
Each tool targets a distinct resource or action: equipment metadata, alarms, buildings, equipment list, schedules, trends, point read, setpoint write. No overlapping purposes.
All tools follow a consistent verb_noun pattern in snake_case (get_, list_, read_, set_). No mixing of conventions.
8 tools are well-scoped for a HVAC building management server, covering inventory, alarms, live data, and control without being excessive.
Covers monitoring and basic control (setpoint write) but lacks operations like schedule modification or alarm acknowledgment, which are minor gaps for the typical use case.