Shell Server
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 |
|---|---|
| terminalA | Run a terminal command and return the output. Args: command: The command to execute in the terminal. Returns: A dictionary containing stdout, stderr, and return_code. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| mcpreadme | Expose mcpreadme.md from the user's Desktop directory. Returns: The contents of mcpreadme.md as a string |
TDQS
Scored across 1 tool
With only one tool, there is no possibility for confusion or overlap. The tool is clearly distinct.
A single tool's name cannot be inconsistent. There is no pattern to evaluate, but no conflicting conventions exist.
A single tool is too few for typical usage. The server would benefit from additional tools like file operations or environment variable management to be more useful.
The server only provides command execution. For a shell server, missing essential operations like reading files, managing directories, or handling processes limits its usefulness and may cause agent failures.