Shellagent MCP 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_app_infoC | Get application information using app_id |
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 for confusion or overlap between tools. The tool 'get_app_info' has a clear, singular purpose that cannot be misselected against other tools.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'get_app_info' follows a clear verb_noun pattern, and there are no other tools to compare it against for inconsistency.
A single tool is too few for a server named 'Shellagent MCP Server', which suggests a broader scope related to shell operations or agent management. This minimal toolset feels thin and incomplete for such a domain, limiting functionality significantly.
The tool surface is severely incomplete. For a shell agent server, obvious gaps include basic operations like executing commands, listing processes, managing files, or interacting with the system. The single tool 'get_app_info' does not cover the expected domain at all, leading to dead ends for agents.