spindl-workshop
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | Yes | The mode to run the server in. Valid values are 'naive' or 'spindl'. |
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 |
|---|---|
| fw_get_device_infoA | Return firewall device details (hostname, model, OS, HA state) |
| fw_get_rulebaseC | Return the full firewall security rulebase |
| fw_get_traffic_logsC | Return firewall traffic logs for the last 24 hours |
| fw_list_toolsA | List all available tools with name, category, and description |
| fw_describe_toolB | Get detailed usage guide for a specific tool |
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
The three fw_get_* tools each target a clearly distinct resource (device metadata, security rulebase, traffic logs), and the two meta tools split cleanly into index (fw_list_tools) versus detail (fw_describe_tool). No two tools overlap in purpose.
Every tool follows the same fw_<verb>_<noun> snake_case convention with a small, predictable verb set (get, list, describe). The shared fw_ prefix further groups all tools under one server namespace.
Five tools is numerically fine, but two of them are introspection/meta tools, leaving only three actual firewall operations. The surface feels thin for a firewall domain, even a read-only workshop one.
Read coverage is reasonable but narrow: logs are hard-coded to the last 24 hours with no time-range or filter parameters, and there are no operations for interfaces, zones, NAT, or rule creation/editing. Agents inspecting a firewall will hit dead ends for anything beyond a snapshot.