cmms-mcp-server
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_plant_overviewA | Counts of assets, active alarms and work orders, overdue work, and critical (A) assets with unacknowledged alarms. Call this first. |
| list_assetsA | List assets, most critical first. All filters are optional and combine with AND. |
| get_assetA | One asset with its uncleared alarms, its active work orders and its last completed work order. |
| list_alarmsB | List alarms, most severe and most recent first. |
| list_work_ordersB | List work orders, highest priority first, then earliest due date. |
| get_work_orderB | One work order with its full history of events (who did what, when, and why). |
| acknowledge_alarmA | Take ownership of an active alarm. Safe to repeat: an already acknowledged alarm is returned unchanged with already_acknowledged=true. |
| create_work_orderA | Create a new work order (status open). Check list_work_orders for the asset first to avoid duplicates. |
| assign_work_orderA | Assign (or reassign) an open or assigned work order. Supervisors only. |
| transition_work_orderA | Move a work order along its life cycle. The assignee or a supervisor can start, hold and complete; only a supervisor can close, cancel, unassign or reopen. Use assign_work_order for open -> assigned. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| shift_handover | Ask the assistant to prepare a shift handover note. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| glossary | Meaning of criticality, severities, statuses, roles and priorities. |
TDQS
Scored across 10 tools
Most tools target a clearly distinct resource+action (overview vs list vs get vs mutate). The only real overlap is assign_work_order vs transition_work_order, but descriptions explicitly carve out the boundary ('Use assign_work_order for open -> assigned'), which mostly resolves it.
Every tool follows a clean verb_noun snake_case pattern (get_plant_overview, list_assets, get_asset, acknowledge_alarm, create_work_order, assign_work_order, transition_work_order). No casing or verb-style deviations.
10 tools is well within the ideal 3-15 range and each one maps to a distinct CMMS capability (dashboard, asset/alarm/WO reads, and key WO/alarm mutations). Nothing feels padded or missing on count grounds.
Work order lifecycle is well covered (create, assign, transition, history), but there are notable gaps: get_asset references 'uncleared' alarms yet no tool clears/resolves an alarm, and there is no way to update a work order or append notes/log entries. Asset creation/editing is also absent, leaving some dead ends.