Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

text_string_escape

Read-onlyIdempotent

Escape or unescape a string for SQL, CSV, shell, regex, PHP, LDAP, XML, or C/C++ syntax. Safely paste data in different code and data formats.

Instructions

Escape or Unescape Strings for Code and Data Formats. Escape or unescape a string for one of eight code/data syntaxes so it pastes safely: SQL, CSV, shell/Bash, regular-expression, PHP, LDAP filter, XML attribute, or C/C++ string. Functionally identical to encoding_decoding_string_escape (same engine, same formats) — either may be used; prefer text_bash_cli_escaper for richer shell/Bash quoting modes, encoding_decoding_url for percent-encoding, or encoding_decoding_html_entities for HTML entities. Runs locally on the supplied text: read-only, non-destructive, offline, rate-limited (~60 req/min). Returns the transformed string plus format metadata, an escaping analysis, and the supported-format map.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe string to escape or unescape. Required, non-empty.
formatYesTarget syntax. sql doubles single quotes; csv RFC-4180 quoting; shell backslash-escapes metachars; regex escapes metachars; php escapes backslash and quote; ldap RFC-4515 hex escapes; xml_attr entity-escapes; c_string C/C++ literal escapes.
operationNoWhether to escape (default) or reverse-unescape the text for the chosen format.escape

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the operation succeeded.
inputNoThe original text, echoed back.
operationNoThe operation performed (escape or unescape).
formatNoThe format used.
resultNoThe escaped or unescaped output string.
format_infoNoMetadata for the chosen format.
analysisNoHeuristic analysis of the input text.
available_formatsNoMap of format id to display label for all supported formats.
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it runs locally, is read-only, non-destructive, offline, and rate-limited (~60 req/min), providing context beyond the 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?

The description is three sentences: first states main function, second provides usage guidance and alternatives, third adds behavioral traits. No wasted words; each sentence earns its place.

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 an output schema exists (implied), the description covers purpose, alternatives, behavioral traits, and parameter semantics. It mentions return value format, making it complete for this tool's complexity.

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% with detailed descriptions and examples for all three parameters. The description adds format-specific escape rules (e.g., 'sql doubles single quotes'), which goes beyond the schema's enum descriptions, though much is already covered.

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 title and description explicitly state the tool escapes/unescapes strings for eight code/data syntaxes. The purpose is specific, with a clear verb and resource, and distinguishes from siblings by naming alternatives.

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 guidance on when to use this tool vs. alternatives (e.g., preferring text_bash_cli_escaper for richer shell modes, encoding_decoding_url for percent-encoding, etc.). It also notes functional identity with encoding_decoding_string_escape.

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