simple-rail-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAIL_IP | Yes | IP address of the linear rail controller. | |
| RAIL_PORT | No | Port of the controller (default 80). | 80 |
| RAIL_ENDPOINT | No | HTTP endpoint for sending commands (default '/command'). | /command |
| MOVE_WAIT_TIME | No | Wait time in seconds after movement (default 5). | 5 |
| COMMAND_TEMPLATE | No | G-code template with {position} placeholder (default 'G0 X{position} F1000'). | G0 X{position} F1000 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| move_rail_and_waitB | Move linear rail to a position and wait for completion. Simple command-based control. |
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 1 tool
There is only one tool, so there is no possibility of confusing it with another tool in the set. Its purpose is clearly stated as moving a linear rail and waiting for completion.
With a single tool, there is no inconsistency across names. The name move_rail_and_wait follows a readable snake_case verb_noun pattern and is descriptive.
A single tool is borderline thin for a server, even one described as simple. If the intended scope is only command-based movement, it may suffice, but typical rail control often needs more operations.
The tool surface covers only moving and waiting, leaving significant gaps for a rail-control domain. Missing operations such as stop, home, get position, or set speed could cause agent failures in common workflows.