Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

text_bash_escaper

Read-onlyIdempotent

Escape or unescape text for safe use in Bash/shell commands using single, double, backslash, or ansi-c quoting styles to prevent metacharacter parsing issues.

Instructions

Bash CLI Shell Escaper. Escape (or, with reverse, unescape) text for safe use on the Bash/shell command line, choosing one of four quoting styles so the string survives the shell's metacharacter parsing intact. Modes: single (wrap in '...', safest, literal), double (wrap in "...", keeps interpolation, escapes \ " $ `), backslash (prefix each shell metacharacter with , no surrounding quotes), and ansi-c (wrap in $'...' with C-style \n \t \NNN octal escapes for control bytes). Prefer this over text_string_escape when the target is specifically a shell command or script; use text_string_escape for SQL/CSV/JS/regex/PHP/XML syntaxes. Runs locally, read-only, non-destructive, deterministic, and rate-limited (anonymous 30/min, 200/hour, 1000/day). Returns the escaped or unescaped string plus the echoed mode/reverse and input/output lengths.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe text to escape, or the already-escaped text to unescape when reverse is true. An empty string is allowed.
modeNoBash quoting style. single='...' literal (safest); double="..." preserves $ and ` interpolation while escaping \ " $ `; backslash prefixes each metacharacter with a backslash and adds no quotes; ansi-c=$'...' uses C-style and octal escapes for control characters.single
reverseNoWhen false (default) escape the text; when true reverse the chosen mode to recover the original string.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoTrue when the operation succeeded.
inputNoThe original text, echoed back.
modeNoThe effective quoting mode used (single, double, backslash, or ansi-c).
reverseNoWhether the request unescaped (true) or escaped (false).
resultNoThe escaped or unescaped output string.
inputLengthNoCharacter length of the input text.
outputLengthNoCharacter length of the result string.
Behavior5/5

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

The description adds context beyond annotations, including that it runs locally, is read-only, non-destructive, deterministic, and rate-limited (with specific limits). It also states the return format (escaped/unescaped string plus metadata). No contradiction with annotations.

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?

Every sentence adds value, covering purpose, modes, usage guidance, behavior, and constraints. The description is well-structured, efficient, and 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 presence of output schema and 3 parameters, the description fully covers behavior, return values, rate limits, and sibling differentiation, making it complete for an agent to use 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 coverage is 100%, but the description enriches parameter understanding by explaining the four modes in detail and the effect of the reverse parameter, adding value beyond the schema's enum 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 it is a Bash CLI Shell Escaper with four quoting styles and reverse operation. It distinguishes itself from text_string_escape by specifying the target use case (shell commands vs. other syntaxes).

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 explicitly advises preferring this tool over text_string_escape for shell commands and directs to the sibling for SQL/CSV/JS/regex/PHP/XML, providing clear when-to-use and when-not-to-use guidance.

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