OmniMCP
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": true,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_devicesA | List all registered hardware devices and their metadata |
| connect_deviceA | Connect to a specific hardware device by ID |
| disconnect_deviceA | Disconnect from a specific hardware device by ID |
| device_statusA | Get connection and health status of a specific hardware device |
| execute_commandB | Execute an action or command on a specific hardware device |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| diagnose_hardware | System prompt and orchestration guide for interacting with factory hardware via OmniMCP |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Available Devices | List of all registered hardware devices, including offline/disconnected ones |
| Connected Devices | List of all currently connected/active hardware devices |
| System Health | Connection and online status overview of all configured hardware adapters |
| Health Checks | Current health status of all registered health checks |
| Widget Examples | Provides metadata and examples for all registered UI widgets |
TDQS
Scored across 5 tools
Each tool has a clear, unique purpose: listing, connecting, disconnecting, checking status, and executing commands. No two tools could be confused for one another.
Most tools follow a verb_noun pattern (list_devices, connect_device, disconnect_device, execute_command), but device_status breaks the pattern by being noun_noun rather than get_status or similar. The inconsistency is minor and does not hinder readability.
With five tools, the server is concise and well-scoped for hardware device management. Each tool earns its place, covering the essential operations without unnecessary bloat.
The surface covers listing, connecting, disconnecting, health status, and command execution, which are core for device management. Missing operations like updating device metadata or removing a device are not clearly required by the stated purpose, so the gap is minor.