MCP Terminal 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_commandC | Execute a command in the local system |
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 tool 'execute_command' has a clear and distinct purpose that cannot be confused with any other tool in this set.
The single tool name 'execute_command' follows a verb_noun pattern, and with only one tool, the naming is inherently consistent. There are no other tools to compare against, so no inconsistencies can arise.
A single tool for a terminal server feels too minimal for the apparent scope. While it covers basic command execution, typical terminal operations might include listing files, navigating directories, or managing processes, suggesting a gap in functionality.
The tool surface is severely incomplete for a terminal server domain. It only allows command execution, missing essential operations like file browsing, process management, or environment inspection, which are core to terminal workflows and will likely cause agent failures.