shopfloor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHOPFLOOR_DB | No | Path to the SQLite database file used by the server (creates a shopfloor.db with demo data if not provided) | |
| SHOPFLOOR_READ_ONLY | No | Set to 1 to run in read-only mode, exposing the data while blocking every write |
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 |
|---|---|
| list_work_ordersB | List work orders, most urgent first (due date, then priority 1 = highest). |
| get_work_orderA | Get one work order with its scheduled blocks. |
| list_resourcesA | List machines and crews that can be scheduled. |
| find_next_slotB | Find the earliest weekday slot where a resource is free for the given number of hours. |
| schedule_work_orderB | Book a resource for a work order. Fails (and changes nothing) if the slot overlaps an existing booking. |
| cancel_blockA | Remove one scheduled block. The work order goes back to 'open' if it has no blocks left. |
| utilization_reportB | Booked vs. available hours per resource between two ISO dates (weekdays only). |
| late_risk_reportB | Flag work orders likely to miss their due date. |
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 has a clearly distinct purpose: work-order listing/retrieval, resource listing, slot finding, booking, cancellation, and two different reports. The scheduling workflow tools are related but not confusable, because their descriptions clearly state different actions and outcomes.
Most names follow a consistent snake_case verb_noun pattern, such as list_work_orders, get_work_order, schedule_work_order, and cancel_block. The two report tools, utilization_report and late_risk_report, are noun phrases without an explicit verb, which is a minor but readable deviation.
Eight tools are well scoped for a shopfloor scheduling server, covering core querying, scheduling, cancellation, and reporting without excessive surface area. Each tool appears to earn its place in the workflow.
The set covers the main scheduling lifecycle: listing and getting work orders, listing resources, finding slots, booking, cancelling, and reporting. Minor gaps remain, such as creating or updating work orders and editing/rescheduling a block directly, but agents can work around these by cancelling and rescheduling.