Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

encoding_decoding_string_escape

Read-onlyIdempotent

Escape or unescape strings for safe use in SQL, CSV, shell, regex, PHP, LDAP, XML, and C/C++ code. Transforms text to prevent syntax errors and injection risks.

Instructions

Escape or Unescape String Literals. Escape or unescape a string for a specific syntax so it is safe to paste into code or data: SQL, CSV, shell/Bash, regular-expression, PHP, LDAP filter, XML attribute, or C/C++ string. Use this for language/format string-literal quoting; use encoding_decoding_url for percent-encoding and encoding_decoding_html_entities for HTML entity conversion. Runs locally on the supplied text: read-only, non-destructive, offline, and rate-limited. Returns the transformed string plus format metadata, an escaping analysis, and the list of supported formats.

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?

The description adds behavioral context beyond annotations: local execution, offline, rate-limited, and output details (transformed string, format metadata, escaping analysis, supported formats). Annotations already declare readOnlyHint=true, destructiveHint=false, etc., and description does not contradict them.

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 concise (4 sentences) and front-loaded with purpose, then usage guidelines, behavioral notes, and return info. Every sentence adds value without redundancy.

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?

The description covers all necessary context: purpose, usage, behavioral traits, and output. With 3 parameters, output schema, and clear sibling differentiation, it is complete for effective tool selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with each parameter having description, examples, and enum values. The description echoes the format list but does not add significant semantic value beyond the schema, meeting the baseline for high coverage.

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 the tool escapes or unescapes string literals for specific syntaxes (SQL, CSV, shell, regex, etc.) and explicitly distinguishes it from encoding_decoding_url and encoding_decoding_html_entities, which are similar sibling tools.

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: 'Use this for language/format string-literal quoting; use encoding_decoding_url for percent-encoding and encoding_decoding_html_entities for HTML entity conversion.' Also mentions it runs locally, read-only, non-destructive, offline, and rate-limited.

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