Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

linux_linux_command_builder

Read-onlyIdempotent

Assemble correct, shell-quoted command strings for 11 Linux tools (find, grep, sed, etc.) from structured fields. Risky flags are flagged with warnings. Does not execute commands.

Instructions

Linux Command Builder. Build correct command-line strings for 11 Linux tools (find, grep, sed, awk, rsync, tar, curl, ssh, scp, ffmpeg, imagemagick) from structured fields, with every argument shell-quoted and risky flags (find -delete, rsync --delete, curl to remote URLs) flagged as warnings. It only assembles command text and never executes anything, so use it to author or template a command you will run yourself; reach for linux_user_group_manager instead when you specifically need useradd/usermod/groupadd account commands, or linux_systemd_unit_generator for unit files. Runs locally: read-only, non-destructive, contacts no external service, rate-limited to 30 requests/minute for anonymous callers. Returns the built command plus per-flag explanations, the files it reads or writes, and safety warnings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNobuild assembles a command from tool plus fields; tools lists every supported command and its sub-form fields; presets lists curated ready-made field sets. Defaults to build.build
toolNoWhich Linux command to build (required only when operation is build). Unknown values return HTTP 400.
fieldsNoPer-tool option map whose accepted keys depend on the chosen tool (for example find uses path, namePattern, size, mtime, fileType, executor; rsync uses src, dst, archive, delete; tar uses operation, compression, output). Call operation tools to discover the exact field names for each command. Omitted or blank fields are skipped; unknown keys are ignored.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoAlways true when the request succeeded.
operationNoThe operation that was performed (build, tools, or presets).
resultNoOperation payload. For build it holds command, explanation, warnings, and files; for tools/presets it wraps the respective catalogue array.
Behavior5/5

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

Annotations provide readOnlyHint, destructiveHint, idempotentHint. Description adds rate limits, local execution, and confirms read-only/non-destructive, matching annotations without contradiction.

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?

Concise description of ~4 sentences, well-organized: purpose, tool list, safety features, usage guidance, parameter hint. No wasted text.

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 output schema exists, description covers all needed aspects: purpose, tool set, safety, usage alternatives, and return values (command, explanations, files, warnings). Sufficient for agent use.

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 description coverage is 100%, so baseline is 3. Description adds value by listing supported tools and advising to call operation tools for field names, slightly improving understanding.

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?

Description clearly states verb 'Build' and resource 'command-line strings for 11 Linux tools', differentiates from siblings like linux_user_group_manager and linux_systemd_unit_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?

Explicitly says when to use (author/template commands) and when not (for user/group or systemd tasks), naming alternative tools. Also notes it never executes commands.

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