Skip to main content
Glama
flujo-app

mcp-sandbox-computer-vm-for-ai

by flujo-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

terminal_execute

Execute bash commands in an isolated Debian Linux sandbox. Use stdin for safe file writes, set working directory or chain commands, and control timeout for long operations.

Instructions

Execute a shell command in an isolated Debian Linux sandbox. Commands run in bash. Each call is independent — no state (shell variables, working directory) persists between calls (however filesystem does persist). Use the working_directory parameter or chain commands with && to control execution context.

To write files or pass data without shell escaping, use the stdin parameter (e.g., command="cat > file.txt" with content in stdin). Commands time out after 120 seconds by default (override with the timeout parameter for long-running operations).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoList of arguments for direct execution (mutually exclusive with command).
stdinNoContent to pipe to stdin.
commandNoShell command string (mutually exclusive with args).
timeoutNoTimeout in seconds (defaults to server config).
temporaryNoRemove the computer when its MCP session shuts down. Set false to keep it provider-side and reconnect by computer_id.
computer_idNoStable computer slug. Omit to create and select a readable random ID for this MCP session.
working_directoryNoWorking directory for the command (must be absolute).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.3

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries full burder. It discloses isolation, lack of state between calls, persistent filesystem, default 120-second timeout, and the stdin overreducing shell escaping issues. This is comprehensive behavioral context beyond just 'execute command'.

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

Conciseness5/5

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

Four sentences with zero waste. The core purpose leads, followed by state semantics, then parameter guidance. Information is front-loaded and each sentence earned its place.

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?

Covers the major concerns for shell execution: sandbox isolation, state persistence, filesystem persistence, working directory, stdin usage, and timeout. The only notable omission is the return/output format, but the description still gives an agent enough to call the tool correctly.

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 already covers all 7 parameters at 100%, but the description adds real context: working_directory for execution control, timeout override for long ops, and an explicit stdin example (cat > file.txt). This goes beyond what the schema fields say.

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?

States clearly that it executes shell commands in an isolated Debian Linux sandbox under bash. The purpose is unambiguous even without sibling tools to differentiate from.

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?

We no sibling tools to compare, it provides actionable guidance: notes statelessness, suggests using working_directory or chaining with &&, and recommends stdin for passing data without shell escaping. Lacks explicit when-not-to-use scenarios, but that is acceptable given no alternatives.

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

Deploy Server

Other Tools