Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SHOPFLOOR_DBNoPath to the SQLite database file used by the server (creates a shopfloor.db with demo data if not provided)
SHOPFLOOR_READ_ONLYNoSet 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 8 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.