IBM MAS Work Order MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAS_HOST | No | Your MAS server URL (no trailing slash) | |
| MAS_LEAN | No | Optional: set to '1' to use lean JSON (smaller responses) | |
| MAS_APIKEY | No | Your API key for authentication (preferred) | |
| MAS_PASSWORD | No | Maximo password if using basic auth | |
| MAS_USERNAME | No | Maximo username if using basic auth |
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 |
|---|---|
| get_work_ordersA | Fetch work orders from IBM MAS with flexible filters. Use this to query open WOs, filter by status, work type, asset, crew, date range, or priority. Returns full WO details including costs, dates, and failure codes. |
| get_work_order_detailA | Get full details for a single work order by WO number, including labor records, materials, costs, failure codes, and all dates. |
| get_asset_work_historyA | Get the complete maintenance history for a specific asset — all work orders ever raised against it, sorted by date. Great for trend analysis, MTTR, and failure pattern identification. |
| get_open_backlogA | Fetch all open (not completed/closed/cancelled) work orders — the current maintenance backlog. Useful for workload planning and identifying overdue WOs. |
| get_overdue_work_ordersA | Fetch work orders where the scheduled finish date has passed but the WO is still open. Essential for SLA tracking. |
| get_pm_complianceC | Fetch preventive maintenance (PM) work orders in a date range and calculate compliance — how many were completed on time vs overdue. |
| get_failure_analysisA | Fetch corrective and emergency work orders with failure codes to analyse breakdown patterns, most common failure types, and assets with repeated failures. |
| get_cost_analysisA | Fetch completed work orders with actual vs estimated costs to calculate cost variance, overruns, and total maintenance spend in a period. |
| get_assetsA | Search for assets in MAS — get asset details, location, status, and description. Useful for looking up asset numbers before querying work orders. |
| get_crew_workloadB | Get a summary of open work orders grouped by crew to assess workload distribution and backlog per team. |
| update_work_order_statusA | Update the status of a work order in MAS (e.g. approve a WO, mark as in progress). Use with caution — this writes to your live MAS system. |
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 11 tools
Most tools have a clear analytical purpose, but several overlap: get_open_backlog and get_overdue_work_orders can both be reproduced via get_work_orders filters, and get_asset_work_history overlaps with get_work_orders filtered by asset. Descriptions help differentiate intent, but the boundaries are not crisp.
All tools follow a consistent verb_noun snake_case pattern: get_* for reads and update_work_order_status for writes. No mixed conventions, no vague verbs.
11 tools is well within the ideal 3-15 range. Each tool addresses a specific maintenance analysis or work order query need without feeling bloated.
The read/analysis surface is comprehensive (compliance, cost, failure, backlog, history), but write operations are limited to status updates — creating work orders, closing them, or editing non-status fields are missing. This is a notable gap for a work order server.