Skip to main content
Glama
realugbun

AgentExecMPC

by realugbun

shell

Execute shell commands securely with configurable timeout and working directory for file operations and system tasks. Includes automatic cleanup and error handling.

Instructions

Execute shell commands in a secure sandboxed environment.

This tool allows executing arbitrary shell commands with built-in safety controls
including timeout limits, working directory restrictions, and process cleanup.
Perfect for file operations, system commands, and shell scripting tasks.

Features:
- Configurable timeout (default: 60s, max: 300s)
- Custom working directory support
- Automatic process cleanup
- Sandboxed execution in workspace
- Comprehensive error handling

Args:
    request: Shell execution parameters including command, timeout, and working directory

Returns:
    ExecutionResponse: Complete execution results with stdout, stderr, exit code,
                      duration, and success status

Examples:
- List files: {"command": "ls -la"}
- Create directory: {"command": "mkdir -p /workspace/new_folder"}
- Run with timeout: {"command": "long_running_task", "timeout": 120}
- Custom directory: {"command": "pwd", "cwd": "/workspace/subfolder"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYes
Behavior4/5

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

With no annotations, the description carries full burden. It discloses key traits: sandboxed execution, configurable timeout (60s default, 300s max), working directory support, automatic cleanup, and error handling. However, it omits details like network access restrictions or persistency of file changes.

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?

The description is well-structured with sections (intro, features, args, returns, examples) and uses bullet points. It front-loads the purpose. However, it is somewhat verbose; e.g., 'sandboxed execution' appears twice and some feature points could be merged.

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

Completeness4/5

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

Given no output schema, the description explains returns (stdout, stderr, exit code, duration, success status). It covers timeout, working directory, error handling, and command constraints (64KB limit from schema, but not in description). It lacks mention of input size limit and does not detail sandbox restrictions, but overall is fairly complete.

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

Parameters3/5

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

Schema description coverage is 0% for the top-level parameter 'request', so the description must compensate. It lists 'command, timeout, and working directory' in Args and provides examples, but does not explain each parameter's semantics beyond what the schema already provides. The examples add value, but not enough to fully compensate.

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 'Execute shell commands in a secure sandboxed environment' with specific verb-resource. It distinguishes from sibling tools 'execute_code' and 'install_package' by focusing on arbitrary shell commands for file operations, system commands, and scripting.

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?

The description provides clear context: 'Perfect for file operations, system commands, and shell scripting tasks.' It implicitly differentiates from siblings but does not explicitly state when not to use or provide alternative suggestions.

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/realugbun/AgentExecMCP'

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