Schema | operational-data-mcp

operational-data-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }
`resources`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
list_assetsB	List all machines / production lines in the operational dataset, with their metadata (type, line, target throughput).
query_productionB	Return hourly production counts, optionally filtered by asset id and/or time range. Time range is ISO 8601 timestamps.
query_downtimeC	Return downtime events, optionally filtered by asset id, time range, or cause code.
summarize_throughputA	Roll up production counts vs. target throughput per asset. Returns total produced, target, attainment ratio, and downtime minutes per asset over the (optionally bounded) time window.
find_anomaliesA	Run simple z-score anomaly detection on production counts. Returns timestamps where an asset's hourly count is more than `threshold` standard deviations away from its mean.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
`assets`	List of machines / production lines in the dataset.
`production`	Hourly production counts by asset.
`downtime`	Downtime events by asset with cause codes.

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/leemarcum/operational-data-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server