digital-twin-mcp
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_devicesA | 列出数字孪生场景中的所有设备（含类型与所在位置）。 |
| get_device_metricsA | 读取设备实时指标，返回指标名 / 数值 / 单位（每次调用推进一个采样周期）。 |
| get_metric_historyA | 读取设备某指标的最近 N 个采样值（时序数据，供趋势图 / 3D 可视化使用）。 |
| set_device_valueA | 写入设备参数（模拟 PLC 写值；也可用于演示故障注入，如手动抬高温度触发告警）。 |
| check_alertsA | 检查告警：不传 device_id 时遍历全部设备，返回 warning / critical 分级告警列表。 |
| get_scene_snapshotA | 数字孪生场景快照：一次调用返回全部设备的坐标、实时指标与分级告警（专供可视化 / 监控轮询）。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| device_health_report | 生成指定设备的健康状态报告。 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| scene_layout | 3D 场景布局资源：设备世界坐标（供 Three.js / Unity / WebGL 等可视化引擎叠加）。 |
TDQS
Scored across 6 tools
Each tool addresses a distinct concern: device enumeration, live metric read, historical metric retrieval, parameter write, alert checking, and a full scene snapshot. No two tools overlap in purpose, and the descriptions reinforce their boundaries.
All tool names follow the verb_noun pattern in snake_case (list_devices, get_device_metrics, get_metric_history, set_device_value, check_alerts, get_scene_snapshot). The pattern is predictable and consistent.
Six tools form a well-scoped set for a digital twin server, covering read, write, history, alerts, and snapshot use cases without bloat. The count is ideal for the domain and avoids both thin and heavy footprints.
The tool surface covers the full lifecycle of interacting with a simulated twin: listing devices, reading live metrics and history, writing values for control or fault injection, checking alerts, and obtaining a complete scene snapshot. No obvious gaps exist for the stated purpose.