Reins
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYTHONPATH | Yes | Path to the reins package so that `python3 -m reins serve` can import it. Should be the absolute path to the reins folder, e.g. /ABSOLUTE/PATH/reins. Also pass the policy file via --policy (e.g. /ABSOLUTE/PATH/reins/policies/simrover.toml) and the binding file via --binding (e.g. /ABSOLUTE/PATH/reins/bindings/simrover-ros-style.toml). |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| driveA | Drive at a constant speed and turn rate for a bounded time, then stop. Runs on a lease of at most 5 s, then stops by itself. Renew with reins_renew. Some calls need the owner's confirmation; those return pending_confirmation. |
| set_ledC | Set the status light. |
| reins_stopA | Stop the robot now. Always allowed. Afterwards motion stays blocked until the owner resumes. |
| reins_statusB | Reins state (stopped?, running lease, pending confirmations) and the robot's status fields. |
| reins_policyB | What this robot's owner allows: actions, bounds, limits. |
| reins_renewA | Extend the running motion lease (heartbeat). At most 5 s from now and 20 s in total. |
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 6 tools
The motion and control tools (drive, reins_stop, reins_renew, reins_status, reins_policy) have distinct purposes, but set_led stands apart from the reins_-prefixed control/state family and could be mistaken for a non-observability action. Boundaries are clear enough that misselection is unlikely.
Names mix plain verbs (drive, set_led) with a reins_ prefix (reins_stop, reins_status, reins_policy, reins_renew), and none of the tools strictly follow a verb_noun pattern. The split between drive/set_led and the reins_ namespace is jarring.
Six tools fit the safety-lease motion domain without bloat; each (motion, stop, renew, status, policy, LED) earns a place. Slightly thin on read-only inspection but reasonable for a control server.
Core motion lifecycle (drive, renew lease, stop, status, policy) is covered, including safety semantics. Minor gaps: no explicit resume or LED read-back and no generic pre-flight validation for flight-like actions, but usable.