rebot-mhs-lab
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discover_devicesA | Discover the available arms, their slots, physical metadata, and safety limits. |
| read_deviceA | Read a device slot: state, position, enabled, or emergency_stop. |
| write_deviceA | Write one device slot. Calls are dry-run by default. Applying motion requires enabled actuators plus both apply=true and confirmed=true. Emergency stop always disables motion. |
| emergency_stopB | Latch the emergency stop immediately and disable the selected arm. |
| plan_two_arm_handoffA | Build a dry-run plan for a two-arm object handoff; never moves hardware. |
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 5 tools
Each tool has a clearly distinct purpose: discovering metadata, reading state, writing state, triggering an emergency stop, and planning a two-arm handoff. There is no meaningful overlap that would cause an agent to select the wrong tool.
Most tool names follow a clear verb_noun pattern: discover_devices, read_device, write_device, plan_two_arm_handoff. The exception is emergency_stop, which is a noun-style command rather than a verb-prefixed action, making the set slightly inconsistent.
Five tools is a well-scoped size for this robotics lab server. Each tool covers a distinct operation and none feel redundant or extraneous.
The tool set covers device discovery, state reading, state writing, safety shutdown, and handoff planning. Minor gaps exist around explicitly executing a planned handoff or resetting a latched emergency stop, but these may be intentionally handled outside the MCP surface or through write_device.