Run shell scripts in Termux to execute commands and capture stdout/stderr, enabling direct device control and automation.
Execute a shell script in the user-installed Termux environment and return stdout/stderr. Requires explicit Termux RUN_COMMAND permission.
| Name | Required | Description | Default |
|---|---|---|---|
| stdin | No | ||
| script | Yes | ||
| workdir | No | ||
| timeoutMs | No |
Changes observed during successful MCP inspections.
v0.6.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructiveHint=true and idempotentHint=false. The description adds the permission requirement but does not elaborate on side effects, error behavior, or state changes beyond what annotations imply.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise—two sentences—and directly states the core action, environment, and permission. No unnecessary words or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
While there is no output schema, the description states that stdout/stderr are returned, which covers the basic expectation. It also mentions the permission prerequisite. However, it lacks details on exit codes, timeout handling, or edge cases like empty script.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has zero parameter descriptions (0% coverage), and the description does not explain any parameters beyond mentioning 'script' and return values. stdin, workdir, and timeoutMs are completely unexplained.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Execute' and the resource 'shell script in the user-installed Termux environment', distinguishing it from sibling tools like android_shizuku_shell. The scope is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives such as android_shizuku_shell or android_shell_status. The only context is the permission requirement, which does not help with tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.