Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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.

A simple MCP server that provides a terminal tool for executing shell commands.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
terminalB
Execute a shell command and return the output.

Args:
    command: The shell command to execute (e.g., "ls -la", "pwd", "echo hello")
    working_directory: Optional working directory to run the command in. 
                      If not provided, uses current directory.
    timeout: Optional timeout in seconds (default: 30.0)
    ctx: MCP context (automatically provided)

Returns:
    A string containing the command output, or an error message if execution fails.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusing it with another. Its purpose—execute a shell command—is explicit and unambiguous.

Naming Consistency4/5

A single tool cannot exhibit inconsistency, and 'terminal' is clear and readable. It is a noun rather than a verb_noun action name, so it does not fully follow the ideal convention.

Tool Count4/5

A shell server naturally needs only one general-purpose execution tool, so the count is well-scoped rather than bloated. It is on the thin side, but additional tools would likely be redundant wrappers.

Completeness4/5

Because arbitrary shell commands can cover file operations, process control, and environment inspection, the surface is functionally broad. Minor gaps exist around streaming output, session persistence, and structured error handling, but these are workable via shell.

Maintenance

ActivityInactive
ResponsivenessOutdated data