Kilntainers
OfficialServer 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 |
|---|---|
| sandbox_execA | Execute a shell command in an isolated Debian Linux sandbox. Commands run in bash. Each call is independent — no state (shell variables, working directory) persists between calls (however filesystem does persist). Use the working_directory parameter or chain commands with && to control execution context. To write files or pass data without shell escaping, use the stdin parameter (e.g., command="cat > file.txt" with content in stdin). Commands time out after 120 seconds by default (override with the timeout parameter for long-running operations). |
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
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'sandbox_exec' has a clearly defined and distinct purpose of executing shell commands in an isolated sandbox environment.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'sandbox_exec' follows a clear verb_noun pattern (exec for execute, sandbox as the context), which would be consistent if more tools were added.
A single tool is generally too few for most server purposes, as it limits functionality and can feel thin. For a sandbox execution server, additional tools for managing files, checking status, or listing processes might be expected to provide a more complete experience.
The tool surface is severely incomplete for a sandbox execution domain. While 'sandbox_exec' handles command execution, there are obvious gaps such as tools for file management (e.g., upload, download, list files), environment inspection, or process monitoring, which are common needs in such contexts.