Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

linux_bash_script_generator

Read-onlyIdempotent

Assemble runnable bash shell scripts from structured options: choose shebang, strict mode, command-line arguments, and reusable blocks like check-root or retry-loop. Returns script text only, never executes.

Instructions

Bash Shell Script Generator. Build a runnable shell script (bash, sh, or zsh) from structured options - it ASSEMBLES and returns script TEXT, it never executes, saves, or runs anything. Pick a shebang and optional strict mode (set -euo pipefail, IFS), declare command-line args (short/long flags with types) that become a getopts-style case parser, and toggle reusable blocks: check-root, check-deps, log-setup, tmpdir (mktemp), trap-cleanup, usage-function, retry-loop, parallel, lock-file (flock), check-internet, and free-form custom blocks; customBody appends your own logic. Operation presets returns 11 ready-made templates (server backup, log rotation, deploy-via-ssh, db backup, rsync, health check, cert renewal, docker restart, git pre-commit, system cleanup). Use linux_systemd_unit_generator for service/timer unit files, linux_cron for crontab schedule lines, and linux_ssh_config_generator for ssh client config - this tool emits the executable script itself. Runs locally: read-only, non-destructive, no netwo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNogenerate builds a script from the options below; presets ignores them and returns the 11 built-in templates.generate
shebangNoInterpreter line. Anything else falls back to bash. Choosing /bin/sh downgrades strict mode to set -eu and warns on bash-only blocks.#!/bin/bash
strictModeNoEmit strict-mode safety flags (set -euo pipefail and IFS). Disabling adds warnings about silent failures.
nameNoOptional script name placed in the header comment.
descriptionNoOptional multi-line description placed in the header comment.
argsNoCommand-line options to parse. Each becomes an UPPER_SNAKE variable plus a case branch; required string/file/int args are validated after parsing.
blocksNoReusable hardening/utility sections to include, emitted in a fixed safe order regardless of array order.
customBodyNoFree-form shell appended as the main script body. Scanned for bash-only syntax when shebang is /bin/sh.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the request succeeded.
operationNoThe operation performed (generate or presets).
resultNoFor generate: the script payload. For presets: a presets array of templates.
Behavior5/5

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

Annotations state readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description reinforces: 'it never executes, saves, or runs anything' and 'Runs locally: read-only, non-destructive.' It adds context that the tool only returns script text, exceeding annotation requirements.

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 a single dense paragraph but well-structured and front-loaded with the main purpose. Every sentence adds value, though a bit lengthy. It could be slightly more concise but remains highly informative.

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?

Given the complexity (8 parameters, 2 enums, output schema exists), the description is complete. It covers purpose, behavior, parameter overview (shebang, strict mode, args, blocks, customBody, operation with presets), and sibling differentiation. No gaps are evident.

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?

With 100% schema description coverage, the description adds meaningful context beyond the schema: it explains that args become 'a getopts-style case parser' and blocks are 'emitted in a fixed safe order regardless of array order.' This adds value beyond the schema descriptions.

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 'Bash Shell Script Generator' and that it 'ASSEMBLES and returns script TEXT, it never executes, saves, or runs anything.' It also explicitly distinguishes from sibling tools like linux_systemd_unit_generator, linux_cron, and linux_ssh_config_generator.

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

Usage Guidelines5/5

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

The description provides explicit when-to-use and when-not-to-use: 'Use linux_systemd_unit_generator for service/timer unit files, linux_cron for crontab schedule lines, and linux_ssh_config_generator for ssh client config - this tool emits the executable script itself.' It also lists the operation presets which are ready-made templates.

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/Jambozx/onlinecybertools-mcp-server'

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