mcp-live-telemetry
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_devicesA | List every simulated machine with its latest reading and state. Returns { count, devices: [{ id, name, state, temperature_c, vibration_mm_s, timestamp }] }. Read only. Use this first to discover valid device ids for the other tools. |
| get_telemetryA | Return time ordered sensor readings for one device across a time window. Inputs: device_id (required), start and end (epoch ms, optional, default last 15 minutes), step_ms (default 30000), limit and offset for pagination, response_format. Returns { device_id, start, end, step_ms, total, count, offset, has_more, next_offset?, readings: [{ timestamp, temperature_c, vibration_mm_s, state }] }. Read only. |
| get_anomaliesA | Detect threshold crossings (temperature or vibration) over a time window. Inputs: device_id (optional, omit to scan all devices), start and end (epoch ms, optional, default last 15 minutes), step_ms (default 30000), response_format. Returns { count, window, anomalies: [{ id, device_id, metric, started_at, ended_at, peak_value, threshold, sample_count }] }. A healthy machine returns no anomalies. Read only. |
| simulate_faultA | Inject a fault on a device so it becomes visible to get_telemetry and get_anomalies. Inputs: device_id (required), fault_type ('overheat' | 'vibration' | 'combined', default 'overheat'), duration_seconds (default 300). The fault is treated as having started two minutes ago so it appears immediately in recent telemetry. Returns { fault: { id, device_id, type, started_at, ends_at, duration_ms }, message }. This tool mutates simulator state; it is not read only. |
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 4 tools
Each tool has a unique and clearly distinct purpose: listing devices, retrieving telemetry, detecting anomalies, and injecting faults. There is no overlap.
All tool names follow a consistent verb_noun pattern in snake_case (list_devices, get_telemetry, get_anomalies, simulate_fault), making them predictable and easy to learn.
With 4 tools, the set is concise but covers all essential operations for a telemetry monitoring and simulation domain. Each tool serves a necessary role without redundancy.
The tool surface covers listing, reading telemetry, anomaly detection, and fault injection. A minor gap is the absence of a tool to cancel an active fault, though faults self-reset after a given duration.