Skip to main content
Glama
luciVuc

Shell MCP

by luciVuc

exec

Run shell commands on the host system, capturing stdout, stderr, exit code, and timeout status. Commands are subject to rate limits and safety blocks for destructive patterns.

Instructions

Execute a shell command on the host system and return its output. Runs the command in a non-interactive shell and captures both stdout and stderr. The response includes the exit code, a timed-out flag, and the full stdout/stderr output. Commands are subject to rate limiting (default 60/min) and a configurable execution timeout. Certain destructive patterns (e.g. rm -rf /, mkfs, dd if=) are always blocked. When the server runs in sandbox mode, network tools (curl, wget), package managers, and process-control commands are also blocked. Sudo commands require the server to be started with ALLOW_SUDO=true. Use this tool for running CLI commands, scripts, build tasks, inspecting the environment, or any operation that can be expressed as a shell one-liner or pipeline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYesThe shell command to execute. Can be a single command (e.g. `ls -la`), a pipeline (e.g. `cat file.txt | grep pattern`), or a compound expression (e.g. `cd /tmp && ls`). The command is passed to the system shell for interpretation. Must not be empty.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses key behaviors beyond annotations (which are absent): non-interactive shell, stdout/stderr capture, exit code, timed-out flag, rate limiting, and blocked patterns. Fully informs agent of constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured: starts with purpose, then output details, then restrictions. Slightly verbose but each sentence adds value. Could be trimmed slightly without loss.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a one-parameter tool with no output schema. Covers all necessary aspects: usage, output structure, constraints, and safety info. No gaps identified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (only 'command' param). Description adds examples (single command, pipeline, compound expression) and a non-empty requirement, going beyond schema to clarify usage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool executes a shell command and returns output. It distinguishes itself from sibling tools like readFile and writeFile by specifying it runs arbitrary commands.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit context: when to use (CLI commands, scripts), limitations (destructive patterns blocked, sandbox mode restricts network/package managers), and prerequisites (sudo requires ALLOW_SUDO). Lacks direct comparison with alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/luciVuc/shell-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server